See the search queries your pages actually win.

What the Search Console integration actually does

You sign in with Google and grant read access to Search Console. Creaiter lists the sites that account can see so you choose the right property, which matters because a domain property and a URL prefix property can report different things for what looks like the same site.

For a given published URL, Creaiter pulls the search analytics that page earned: the queries it appeared for, how many impressions and clicks each query produced, and the average position. That is the difference between believing a piece targets a keyword and knowing which keywords it is actually being shown for.

• Sign in with Google, pick which Search Console property to read
• Queries, impressions, clicks and average position for a published page
• Reporting attached to the piece in your content repository, not a separate export
• Feeds the keyword side of Creaiter with what the page really ranks for
• Read only access, so nothing in your Search Console account is altered

How to connect Search Console

The setup is a Google sign-in. There is no HTML verification file to upload, because Creaiter reads a property you have already verified with Google rather than verifying a new one.

• Verify your site in Google Search Console first, if you have not already
• In Creaiter, open Settings, then Integrations
• Choose the Search Console card and sign in with Google
• Grant read access when Google asks
• Pick the site property you want Creaiter to read
• Publish or link a page, since page level query data needs a live URL

The row cap, and why we mention it

Search Console returns at most twenty five thousand rows per request. A page with a long tail wider than that comes back cut off, and any total calculated from the cut list is a sample, not a total.

Creaiter says so when a report hits that ceiling. It would be easy to print the number and move on, and most tools do, because a caveat looks worse in a screenshot than a clean figure does. A number you cannot trust is worse than a number with a warning attached to it, so the warning stays.

The same rule applies to failures. If the read did not succeed, Creaiter says the read did not succeed. It does not render a zero and let you draw the wrong conclusion about a page that is doing fine.

What day to day looks like

You publish a piece. A few weeks later, once Google has had time to index and show it, you ask what it is ranking for. The answer names the actual queries, which is usually more interesting than the keyword you set out to target.

That gap is the useful part. The queries you did not plan for are where the next piece comes from, and having them attached to the original article is what makes the next brief write itself.

What the Search Console integration does not do

Everything below is outside this integration. Some of it is outside Creaiter entirely.

• It does not verify your site with Google. You verify the property, Creaiter reads it
• It does not submit sitemaps, request indexing, or make any write to Search Console
• It does not fix technical SEO issues such as crawl errors, redirects, or page speed
• It does not audit or build backlinks, and it does not report referring domains
• It does not report paid search, because Creaiter does not run paid advertising
• It is not a sales CRM and does not connect a query to a deal