Google Search Console: what is and isn't supported
Verifying your site: paste the tag here, click Verify there
You own the domain, so you can verify it in Search Console yourself, and the token field on the Edit screen makes the HTML-tag method a paste: the tag goes on every page, then you click Verify in Search Console. Nothing here blocks that, and nothing here depends on it.
What we will not do is ask for your Google account so we can show you a chart you already have. An extra sign-in that adds no fact is a liability, not a feature. Query data is Google's report about your site, and it is best read where Google publishes it.
Verification is not a prerequisite either. A site publishes, gets its sitemap and its metadata, and is reachable whether or not you ever open Search Console.
What the Metadata screen shows
For every page on a site, the Metadata screen shows the real title tag, the meta description and the H1 that search engines and AI tools would see. Real values, measured against the lengths the publish gate checks.
It is a read-only view. To fix something, use Edit copy on the Pages screen, where the title, supporting line and search description can be changed on every page. Or ask the assistant to change it for you.
This is what most people really want from Search Console — not the query report, but proof that a page says what they think it says. Each page is individually built, so it is worth checking every one.
Indexing choices stay in your hands
Robots and indexing controls live in the product. Whether a site is open to crawlers is a choice you make, not a default you find out about later.
Separately, you choose whether Google may use your content to train its AI. Search indexing is unaffected either way. Those two questions get mixed up constantly, and two plain switches is the only honest way to answer both.
What we are accountable for
Search results are a third party's judgement, and no honest product reports them as its own output. What we control is the page, so that is what gets checked. Every page is checked before it publishes, by checks that draw on Google Search Essentials and other public standards and on our own quality rules, and each site is scored against the platform's publish check, which has 51 checks in nine groups.
That makes the split of labor clean. The compliance gate governs what leaves the building, and the Metadata screen shows exactly what a crawler will read. Search Console then tells you what Google did with it.
Keep them in that order. Get the page genuinely useful first, confirm what a crawler receives second, and read a third party's verdict third, in their own tool.
Updated October 2026
Frequently asked questions
Can I link Search Console to my account?
Verification, yes: paste the HTML-tag token from Search Console on the Edit screen and the tag goes on every page, then click Verify in Search Console. Reading Search Console data inside the product is not offered yet.
Can I verify my microsite's domain in Search Console myself?
Yes. You own the domain, so you can verify it in Search Console directly.
Where do I check my titles, descriptions and H1s?
The Metadata screen shows the real values for every page, measured against the lengths the publish gate checks.
Does opting out of Google AI training affect indexing?
No. You choose whether Google may use your content to train its AI, and search indexing is unaffected either way.
See it built for your business
Every plan starts with a 15-day free trial — build a site in conversation and watch it pass the compliance gate before you decide.
See plans — from $99/moBuild it compliant from day one
Every page is checked before it goes live, by checks that draw on Google Search Essentials and on our own quality rules.
Start your 15-day free trial →Check a site you already have
Free: is your site safe with Google? Get an SEO + compliance score.
Try the Microsite Compliance Grader →