GOOGLE MERCHANT CENTER ACCOUNT SETUP: THE ORDER THAT AVOIDS VERIFICATION BLOCKS

Most walkthroughs treat google merchant center account setup as a linear wizard: sign up, type your URL, click verify, done. Then you're staring at a red "not verified" banner with no idea why. After running Shopping on live accounts since 2021, I've learned that the wizard isn't the hard part the order you do things in is. Get the sequence right and verification passes on the first try; get it wrong and you fight blocks for days over a setup that should take twenty minutes.

This article is about that sequence. I'm not going to narrate every screen Google's UI shifts and you can follow the prompts. What I want to give you is the order I actually use, learned from cleaning up dozens of stalled accounts: what to prepare before you start, when to create the account, and exactly when to verify and claim so the system has everything it expects at the moment it checks. The mistakes I see aren't usually inside the wizard. They happen because someone did step three before step one.

So the lens here is operational. Treat the setup as a pipeline where each stage depends on the one before it, and the verification block the single most common stall mostly disappears. Rush the stages out of order and no amount of re-clicking "verify" will fix a signal that isn't in place yet.

Before you create google merchant center account: get the site ready first

The biggest lever in the whole process is something you do before you ever open the signup screen. Before I create google merchant center account for a client, I make the website itself ready to be verified. That means the domain is live on HTTPS with no SSL warnings, the homepage loads cleanly, and the policy pages a reviewer looks for returns, shipping, contact, privacy actually exist and are linked from the footer. A thin or broken storefront gets flagged the moment a human looks at it, no matter how clean the signup was.

The second thing I sort out first is ownership. If the site already has Google Search Console or Google Analytics set up under the same Google login I'll use for Merchant Center, verification often happens automatically the instant I enter the URL no tag, no email code, no block. That single bit of preparation is the difference between a frictionless setup and a manual verification scramble. So I confirm I'm logged into the correct Google account, because one Google login maps to exactly one Merchant Center account and the wrong one creates a mess later.

Finally, I match details. The business name I'll type into the account should read the same as it does on the site, and the URL I'll enter should be the exact domain I control not a marketing redirect. These sound trivial, but mismatches here are a quiet, common cause of the verification problems covered in Merchant Center feed verification. Prepare the site, line up ownership, match the details then, and only then, open the wizard.

Step one: create the account and enter business information

With the site ready, the account itself is the easy part. You go to the Merchant Center sign-in page, sign up for free, and tell Google about your business where you sell (online, in store, or both), your business name, and your store's website address. This is the stage everyone rushes, and it's also where one irreversible decision hides.

The country you select during setup is permanent. It can't be changed afterward, and it sets your time zone and several downstream defaults, so I always stop and double-check it before continuing the only "fix" for a wrong country is starting over with a different Google login. Beyond that, I fill the business information completely and accurately rather than skimming, because half-filled business details are themselves a reason accounts get held for review. A google merchant account that looks like a real, fully-described business clears the trust bar far faster than a sparse one.

When I enter the website address at this stage, I use the exact URL the site lives on. If you have ownership already in place from the preparation step, Google frequently verifies the store automatically right here, and you'll see a notice that your online store was verified during setup. That's the whole payoff of doing the site work first verification can resolve itself before you even reach a verification screen. If it doesn't auto-verify, that's fine; the next step handles it deliberately.

Step two: verify, then claim two steps, not one

This is the stage people collapse into a single action, and it's the most common reason a setup stalls just short of done. Verifying and claiming are separate. According to Google's own documentation on online store URL verification, verifying tells Google you own the site, while claiming reserves that URL exclusively for your account so no one else can submit products under your domain. You verify first; only then can you claim.

If automatic verification didn't fire, you pick a method: an HTML meta tag in the homepage head, an HTML file upload, email verification, Google Tag Manager, or Google Analytics. I default to the HTML tag for full control, and the rule that saves the most grief is simple put the tag in the head, before the body, and never remove it. The tag has to stay in place permanently; people verify, delete the tag a week later, and lose verification, which then drags the claim down with it.

Once verified, you click claim. I've watched accounts sit "verified but not claimed" for weeks while the owner wondered why nothing would serve, because they assumed verification was the end. It isn't. After claiming, the URL is exclusively yours, and if you'd already built a feed you'll need to re-fetch it. Do these in order verify, confirm, then claim and the gate that blocks most setups simply opens.

The three verification blocks I hit most and the order that prevents them

Almost every verification block I clean up is one of three things, and each maps back to a step done out of order. The first is a URL mismatch: the address entered in Merchant Center doesn't match the property you actually own and control. Preparing ownership first and typing the exact domain not a redirect, sometimes without the "www" heads this off before it starts.

The second is the tag problem: the HTML meta tag was placed outside the head, modified, or removed after verification. Because I verify only after the site is ready and I leave the tag permanently in place, this block rarely appears. The third, and the most frustrating, is a domain already claimed by another Merchant Center account often an old or test account nobody remembers. You can only claim the highest domain level you need, and a claim at a higher level blocks lower ones, so I check for orphaned claims before assuming the system is broken.

The pattern across all three is the same: verification blocks aren't random, they're the system reporting that an ownership signal isn't where it expected it. Sequence the setup so every signal is in place before the check runs, and the blocks stop being a wall. This is exactly why I lead with site readiness when I onboard the whole Google Shopping system the verification stage only behaves when everything upstream of it already does.

After verification: what to finish before you build a feed

Verifying and claiming gets you through the door, but the account isn't truly ready until a few business settings are in place. I set up shipping so it matches what the website promises, configure return policies consistently, and where it applies handle tax settings, because each of these is checked and a mismatch against the live site causes disapprovals later. The discipline that defines the cross-check is the same one that defines setup: Merchant Center and the storefront have to tell the same story.

Only after that do I move to products. The order matters here too: a clean, verified, fully-configured account first, then the feed built on top of it. When the feed goes in, it has to meet the Google Shopping product feed requirements mandatory attributes, valid prices, identifiers but those problems are far easier to diagnose when the account underneath is already stable. Building the feed before the account is solid just stacks two layers of failure on top of each other.

I treat the finished setup as the launchpad, not the destination. Once the account is verified, claimed, and its business settings agree with the site, the campaign you eventually build sits on a foundation that won't surprise you which is the entire point of doing google merchant center account setup carefully rather than quickly.

The practical takeaway

If you remember one thing about google merchant center account setup, make it the order. Prepare the website first HTTPS, policy pages, and ownership already in place. Then create the account, double-checking the permanent country field. Then verify and claim as two distinct steps, leaving the verification tag in place forever. Then configure the business settings and only afterward build the feed. Verification blocks almost always trace back to one of those steps being skipped or done early.

Work in that sequence and the setup that frustrates so many people becomes routine. The block you were bracing for never appears, because by the time Google checks for an ownership signal, you've already put it exactly where the system expects to find it. That's the difference between fighting Merchant Center and simply satisfying it before you launch a single ad.