Google Search Console integration

Google Search Console shows which pages Google has indexed, which queries bring clicks, and how real visitors experience page speed. Framer and Webflow both take Google’s verification tag in site settings and publish a sitemap for you; on Astro and Next.js we add the tag in code and build the sitemap with the site. Your company owns the property and we work in it as a user.

Updated

Official sources

  1. Add a website property (opens in a new tab)Search Console Help · support.google.com
  2. Verify your site ownership (opens in a new tab)Search Console Help · support.google.com
  3. Managing owners, users and permissions (opens in a new tab)Search Console Help · support.google.com
  4. Performance report (opens in a new tab)Search Console Help · support.google.com
  5. Page indexing report (opens in a new tab)Search Console Help · support.google.com
  6. Core Web Vitals report (opens in a new tab)Search Console Help · support.google.com
  7. Change of Address tool (opens in a new tab)Search Console Help · support.google.com
  8. Site moves with URL changes (opens in a new tab)Google Search Central · developers.google.com
  9. How to connect Google Search Console to your Framer site (opens in a new tab)Framer Help · framer.com
  10. Google site verification (opens in a new tab)Webflow Help · help.webflow.com
  11. Create a sitemap in Webflow (opens in a new tab)Webflow Help · help.webflow.com
  12. @astrojs/sitemap (opens in a new tab)Astro docs · docs.astro.build
  13. generateMetadata (verification) (opens in a new tab)Next.js docs · nextjs.org
  14. sitemap.xml (opens in a new tab)Next.js docs · nextjs.org

Checked against the official docs on. Tools change often; we re-check before every build.

Press Escape to close.

Google Search Console integration at a glance
ComplexityLow
Method
  • Framer: Native
  • Webflow: Native
  • Astro: Native
  • Next.js: Native
Typical setup1 to 2 hours
What we doWe verify the property, submit the sitemap, give your team and ours the right access, and check indexing after launch.
CategoryAnalytics

Setup by platform

How we set up Google Search Console

  • Framer

    • Native

    Framer documents a URL-prefix property: paste Google’s meta tag at the end of the head in the site’s General settings and republish. Framer builds /sitemap.xml on its own; we submit it in Search Console.

    Framer development
  • Webflow

    • Native

    Site settings, SEO tab: paste the verification ID into the Google site verification field and publish. Auto-generate sitemap in the same tab rebuilds /sitemap.xml on every publish and adds it to robots.txt.

    Webflow development
  • Astro

    • Native

    The official @astrojs/sitemap integration writes sitemap-index.xml at build and needs the site URL in the Astro config. We verify with a DNS record, or a google-site-verification meta tag in the shared layout.

    Astro development
  • Next.js

    • Native

    verification.google in the root layout’s metadata renders the google-site-verification tag. app/sitemap.ts returns the list of URLs, which we build from routes and CMS entries, and Next.js serves it at /sitemap.xml.

    Next.js development

Use cases

What teams use it for

  1. Indexing after a launch or migration

    Submit the new sitemap, then filter the Page indexing report by sitemap to see which new URLs Google has picked up and why others aren’t indexed.

  2. Queries that bring clicks

    The Performance report shows clicks, impressions, CTR and average position per query and page, so content work starts from real searches.

  3. Core Web Vitals from real users

    Field data from the Chrome UX Report, split by mobile and desktop, shows what visitors actually experience, not a lab score.

Before you add it

What to watch out for

  • Data layer

    The numbers run behind

    The newest days in the Performance report are preliminary and can still change. Core Web Vitals cover the last 28 days, and pages with too little traffic show no data.

  • Limits

    Migrations keep the old property

    Keep the old property, verify the new one and submit its sitemap. Change of Address is only for a new domain or subdomain, not for HTTPS, www or path changes.

  • Security

    You own it, we use it

    Your company’s Google account verifies the property and we join as a user, so you can remove us at any time. Leave the verification tag or DNS record in place, or ownership lapses.

FAQ

Questions about Google Search Console

Adrian

Can't find your answer?

Book a call and let's talk.

Or email us  hello@designme.agency

Domain property or URL-prefix property?

A Domain property covers every subdomain plus http and https, and verifies only through a DNS record. A URL-prefix property covers one exact address and accepts a meta tag, which is the route Framer and Webflow document.

When we have DNS access, we add a Domain property as well, so no subdomain falls outside the reports.

Do we need a new property after a migration?

Not if the domain stays the same: the property and its history carry on, and you submit the new sitemap. Keep the existing verification tag on the new site, or Google may stop detecting it.

If the domain changes, verify the new one, keep the old property, and file a Change of Address from the old property once the 301 redirects are live. The same owner account must own both, and Google advises keeping the redirects for at least a year.

Why is the Core Web Vitals report empty?

It uses field data from real Chrome users. A new property can take a few days to fill, and a group of pages with too little traffic shows no data at all.

You've reached the end, so now…

Tell us what you’re building.

We’ll help you map the right scope, team, timeline, and next steps.

Book a call