Shopify theme detector for a Shopify media buyer

What a media buyer is deciding

You are deciding whether a landing URL can take more spend. Shopify theme finder covers the part you can see without the client’s admin: the public page, the public ads, or the unit economics they sent you. More of that work is covered for Shopify media buyers. Shopify theme finder is the check for this part of it. Paste the store URL.

What to hand someone else

Send the theme name and whether it is from the Theme Store. The estimate starts there.

Open another tool only when the next question is different. Shopify theme finder is enough for this one.

The week you pin a theme name to a product URL

Pick one product URL and stay with it for the week. Use kids backpack if that is what you are selling now, at 48, on the template the product actually uses. On Monday you run the public theme check and write the name, Theme Store or custom, and the admin nickname if you have a login. You do not redesign on Monday. A name without a template is a sticker. A template without a name gets edited on the wrong copy by Wednesday.

On Tuesday you open Shopify admin, Online Store, Themes, Customize, and the product template dropdown. You select the template for that URL. You click the product form and write whether it still holds title, price, variant picker, and buy buttons. You list the sections above and below the form in order. You mark any section that is an app block. You save the list in the same note as the theme name. That list is the baseline the rest of the week is allowed to change.

On Wednesday you decide the smallest edit that matches the baseline. Maybe you move one section. Maybe you fill a rich text block you found empty. Maybe you do nothing because the template already has a place for the story and the story is the missing piece, which is a writing task. You make the edit on a duplicate theme if the shop is live and the change is visible. You do not publish a different theme family on Wednesday to see how it feels.

On Thursday you check app embeds on the theme copy you are judging. You make the duplicate honest before you have opinions. On Friday you look at the live URL if you published, or at the preview URL if you did not. You click each variant. You confirm the price. You file the note where next week staff can find it. The week fails if Friday taste comments are about a different template than Monday name.

Fields that keep the week from resetting

Keep a single running note with fixed fields: date, domain, public theme name, origin label, admin nickname, published or not, product title, template name, form status, section order, embeds checked yes or no, change made, who edits next. Fixed fields sound bureaucratic until two people edit two copies and both think they are on the live shop. The fields are how you notice.

Write the product facts beside the theme facts without mixing them. kids backpack and 48 can change because of a sale, a supplier, or a test. The theme name does not change when the price does. If you overwrite the note every time the price changes, you will lose the template name. Add price updates as new lines. Leave Monday theme lines intact.

When someone proposes a new theme mid-week, they must name a section the current template cannot add. Park the proposal at the bottom of the note. Do not start a second project beside the unfinished baseline. Two themes in one week without a publish decision is how embeds drift and how the product form gets checked on a preview nobody buys from.

If you lack a login on Monday, the public name is still worth having. Mark the editor fields as blocked, not as blank forever. The week then produces a question for the store owner instead of a fake section list. Inventing the section order from memory is worse than waiting. The detector did not see inside the editor, and neither did you.

The handoff that travels with the name

Hand off three objects: the note, the theme copy to edit, and the product URL. In the message, name the person who may publish and the person who may not. Publishing is the step that changes what buyers load. Section edits on an unpublished copy can wait for review. Embeds on the published theme should not be toggled by someone who thought they were in a sandbox.

Tell the next person what done means. Done means the URL shows the agreed section change and the product form still presents title, price, variants, and buy buttons. Done does not mean a new homepage. Done does not mean a speed grade. Done does not mean they installed an app that duplicates a section. If you want a design opinion, ask for it on the named template after the done condition is met, not before.

If the next person is a developer, add whether file edits are in scope. Default is no. Sections first. If they believe files are required, they reply with the file and the buyer-facing reason, and they wait. The theme name tells them which theme upstream they are in, Theme Store or custom. It does not grant code access by itself.

Keep the handoff shorter than the week. A long lecture gets skimmed. The five Monday lines plus the section order plus the one job is enough. Link the tools only as paths they can rerun: /theme-detector/ for the public name, /app-detector/ if their job turns out to be embeds. You do not need to paste a tour. They have admin.

What you recheck on the live product URL

Halfway through the week, load the product URL the way a buyer would, logged out, on a narrow window. Confirm you are still on the theme named on Monday by checking the published theme in admin, not by trusting a preview bar left open from Tuesday. For kids backpack, read the title, read 48, choose every finish the product actually sells, and press the buy button far enough to see the cart line. If any of those miss, stop section work and repair the form before you debate spacing.

Use the live URL to catch template assignment mistakes. If the page does not show the sections you listed, the product may point at a different template than the one you edited. Fix the pointer or edit the template the product really uses. Do not duplicate the same sections onto a second template "just in case" unless you mean to maintain both. Two templates with drifting copy become two products wearing one name.

Note anything that appeared which is not in your section list. A bar, a badge, or a chat bubble usually came from an app embed on this theme. Write the surprise down and leave the embed decision for an app pass. Hiding it inside a theme argument will send you looking for a new theme when the toggle is already in theme settings. The live URL is a witness. It is not a scoreboard, and it does not tell you the page is fast.

If you are on an unpublished copy, say so in the note and do not call that URL live. Send stakeholders the preview they can open, plus the theme nickname. When someone replies with comments on the homepage, redirect them to the product URL in the note. The week only has one page in scope. Comments on other pages can be captured at the bottom and ignored until this URL matches the section order you wrote down.

The theme behind the URL your ads already use

Your ads send people to a product URL. That URL renders inside the published theme, on one template. Before you change bids or creative, write the theme name and the template name for kids backpack. If an editor publishes a new theme while an ad is live, your click still lands, but the form, the headline section, and the embeds may move. You will read that movement as an ad problem. Pinning the theme name is how you notice the page changed under you.

This week, do not swap themes. Do not authorize a homepage project. Open the product template and check that the first screen a cold visitor sees still contains the same promise as the ad, and that 48 is the price the ad implies. If the ad says a finish, the variant picker should include that finish. Those are template checks. They are in your lane because they change what the click buys. Art direction beyond that can be requested as a section edit with the theme name attached.

Your handoff to the person who owns the theme is a frozen URL plus a short exception list: what must not move while the test spends. Typical lines: do not publish a different theme, do not replace the product form, do not add a popup embed on this theme, do not change the variant names. You are not forbidding all merchandising. You are dating the freeze to the flight. When the flight ends, they can resume section work.

If the public theme is a renamed Dawn, say so in the handoff so nobody treats a simple section move as a three-week build. If the public theme is custom, say that file edits are out of scope unless the form is broken. Media time should not fund a surprise rebuild. When the landing experience is wrong, describe the mismatch in buyer language: the ad offers a desk stand in black, the template opens on a bundle. That sentence is more useful than a moodboard.

Friday you archive a screenshot of the live URL with the theme name in the filename, next to the ad name. You are not claiming the screenshot improved anything. You are making the next anomaly comparable. If next week conversion talk starts, you can see whether the template still matches the one you bought traffic for. If it does not match, you pause the interpretation, not the learning.

Shopify questions