How Do I Set Up Google Search Console for a New Webflow Site?

Why do my new Webflow pages not show up in Google yet?

Most likely because Google does not know they exist. A fresh Webflow site is not automatically in Google's index. You have to tell Google it is there, prove you own it, and hand over a map of your pages. Google Search Console is the free tool that does all three, and setup takes under an hour.

I set this up on the first day of every new site I build. It is the difference between guessing whether Google sees your work and knowing. Without it, you are flying blind on which pages get found and which ones Google skips.

This guide walks through the whole process for a Webflow site: verifying ownership, turning on your sitemap, submitting it, and asking Google to index your key pages. No code, no plugins, just the settings that already exist in Webflow and Search Console.

What is Google Search Console, and do I need it?

Google Search Console is a free Google tool that shows how your site appears in search. It reports which pages are indexed, what queries bring visitors, and what errors Google hit while crawling. If you want your site found on Google, you need it. There is no paid tier and no real alternative for this data.

Think of it as a direct line to Googlebot. Analytics tells you what visitors do once they arrive. Search Console tells you the step before that: whether Google can find, crawl, and index your pages at all. Those are different questions, and this tool owns the second one.

Every site I run has it connected, old and new. It is where I confirm a redesign did not drop pages, where I spot a sudden crawl error, and where I check that new posts get picked up. For a founder, it is the single most useful free tool for search, full stop.

How do I choose between a Domain and a URL prefix property?

Google offers two property types. A Domain property covers your whole domain, every subdomain and protocol, but it can only be verified with a DNS record at your registrar. A URL prefix property covers one exact address, like https://yourdomain.com, and gives you easier verification options, including a simple meta tag.

For most Webflow sites, I pick the URL prefix property. It lets you verify straight from Webflow's own settings without touching your DNS, which is faster and less error-prone for a new owner. You just add the exact address you use, matching the https and www version your site actually serves.

A Domain property is the more complete option because it captures everything under your domain. If you are comfortable adding a DNS TXT record at your registrar, it is worth doing later. But to get started today, the URL prefix path is the one I recommend, and it is what the rest of this guide uses.

How do I verify my Webflow site in Search Console?

Use the HTML tag method, which pairs cleanly with Webflow. In Search Console, add a URL prefix property and choose the HTML tag option. Google shows a meta tag. Copy only the verification ID, the string inside the content attribute, then paste it into Webflow's Site Settings under the SEO tab.

Webflow has a field made for exactly this. Open Site Settings, go to the SEO tab, and find the Google Site Verification field. Paste only the ID string there, not the whole meta tag. This is the step people get wrong most often, so it is worth double-checking before you move on.

Then you must publish. Webflow only writes that verification tag into your live site when you publish, so save the setting, publish the site, and go back to Search Console and click Verify. If it fails, nine times out of ten the site was not published after saving, or the whole tag was pasted instead of just the ID.

How do I turn on and find my Webflow sitemap?

Webflow can build your sitemap for you. In Site Settings under the SEO tab, turn on 'Use auto-generated sitemap,' then publish. Webflow creates a sitemap that lists every live page and updates it each time you publish. You can then find it at yourdomain.com/sitemap.xml in any browser.

A sitemap is just a file that lists your pages so Google does not have to guess what exists. The auto-generated one covers your whole live site by default. If you want to keep a page out of it, use the Sitemap indexing toggle in that page's own settings, which is handy for thank-you pages or drafts.

Before you submit it, open yourdomain.com/sitemap.xml and confirm it loads and lists your real pages. If you use Webflow Localization or need custom control, Webflow also lets you paste a custom sitemap instead. I cover how this fits with your other crawl settings in my post on Webflow SEO settings for canonicals, robots, and sitemaps.

How do I submit my sitemap to Google Search Console?

Once your property is verified, open the Sitemaps report in Search Console, type sitemap.xml into the 'Add a new sitemap' box, and click Submit. Google will fetch the file, read your list of pages, and use it to guide crawling. You only submit the path, since Google already knows your domain.

After you submit, the status should read 'Success' within a short time. If it says 'Couldn't fetch,' give it a few minutes and refresh, since a just-published site can take a moment. Confirm the sitemap URL actually loads in your browser first, because a sitemap that does not load is the usual reason a submission fails.

Submitting a sitemap does not force Google to index every page, and it is not a ranking trick. It simply makes sure Google has a clean, current list to work from. Search engines still decide what to index on their own. If you also care about AI crawlers, my guide to your sitemap and AI search engines goes deeper on that angle.

How do I ask Google to index a specific page?

Use the URL Inspection tool at the top of Search Console. Paste in the full address of a page, press enter, and Google shows whether that URL is indexed. If it is not, click 'Request indexing' to add it to a priority crawl queue. This is how I nudge a brand-new page to get seen faster.

I use this for pages that matter most, like a new service page or a fresh article I want found this week. It is not a magic button, and Google may still take time, but it beats waiting for the next scheduled crawl. Do not spam it on the same URL, since repeated requests do not speed things up.

URL Inspection also shows why a page might be missing. It reports the last crawl, the status code Google saw, and whether the page was blocked. That ties straight into knowing your codes, which I break down in my post on HTTP status codes that matter for SEO.

What reports should I check first?

Start with two: the Pages report and the Performance report. The Pages report shows how many URLs Google has indexed and lists reasons for any that are not, like 'not found' or 'excluded.' The Performance report shows the real queries, clicks, and impressions your site earns in search.

The Pages report is your health check. On a new site, it is normal to see only a few pages indexed at first, with the count climbing over the following weeks. What you watch for is errors, like pages Google could not crawl or duplicates it chose to skip. Those are the ones to fix.

The Performance report is where the payoff shows up. Once data builds, you can see which pages and search terms bring people in. I use it to find pages that rank on page two and could climb with a small content push. It turns guesswork into a clear list of what to improve next.

How long until I see data in Search Console?

Expect a wait. Verification is instant, but real crawl and Performance data usually take a few days to a couple of weeks to fill in for a new site. Google has to crawl your pages, decide what to index, and then log the searches that show them. Patience here is normal, not a sign of a problem.

In the first days, do not panic if the reports look empty. That is expected. Check that your sitemap shows 'Success,' that a few key pages are indexed, and that there are no crawl errors. Those early signals matter more than traffic numbers, which simply have not had time to build yet.

Come back after a week and the picture changes. More pages appear as indexed, and the Performance report starts to show impressions. From there, checking in once a week is plenty. Search Console rewards steady attention, not daily refreshing.

What should I do after setup?

After setup, make three habits: submit your sitemap once, request indexing on any important new page, and check the Pages and Performance reports weekly. That routine keeps Google's view of your site current and catches problems while they are small. It is a few minutes a week for a real edge.

You can also connect Bing Webmaster Tools with the same sitemap to cover more search engines. But Google Search Console is the priority, since it drives the bulk of most sites' search traffic. Get it solid first, then expand.

If you would rather have someone set this up cleanly and hand you a site that is already talking to Google, I am happy to help. I do this for founders and small teams as part of every build. Reach out through pravinkumar.co and let's connect about getting your pages found.