How to Index a New Website on Google with TurboIndex

To get a new website indexed with TurboIndex you verify the site in Google Search Console, sign in to TurboIndex with the same Google account, add the site, and give the indexing account Owner access to the property through one of three paths. From that point the service reads your sitemaps, fetches every page with TurboIndexBot to check that it can be indexed, asks Google for the status of each URL, and submits the ones that are not indexed, up to 200 a day. Google decides what to index; the dashboard shows you, per page, what it decided.

This is the whole process, with what to expect at each step.

Before you start: the site must be in Search Console

TurboIndex works from your Search Console properties, so the site has to be verified there first. Open search.google.com/search-console, click Add property, and pick one of the two types:

• Domain property (yoursite.com): verified with a DNS record, covers every subdomain and both http and https. Pick this when you can edit DNS. It is the one with the fewest surprises later.
• URL-prefix property (https://www.yoursite.com/): verified with an HTML file, a meta tag or Google Analytics, covers only URLs that start with that exact prefix. If your pages live on www. and you verified the non-www prefix, the property does not cover them.

While you are there, submit your sitemap under Indexing, Sitemaps. TurboIndex reads the sitemaps listed in Search Console first, and a submitted sitemap is also what Google itself uses. If you are not sure the file is valid, run it through the sitemap validator. The rest of the Search Console basics, including what each report is for, are in the Search Console beginner's guide.

Step 1: sign in with Google

Click Continue with Google on TurboIndex and choose the account that has the property. Google shows a consent screen asking for your name and email, and for View Search Console data for your verified sites. That second permission is read-only: it lets TurboIndex list your properties, read the sitemaps you submitted and ask the URL Inspection API about your URLs, and nothing more.

Step 2: add the site

After sign-in the dashboard lists every property your account can see, with your permission level next to each. Click Add site on the one you want. The free plan covers one site; the paid plans cover 3, 10 or 50.

If you have both a Domain property and a URL-prefix property for the same site, add the Domain one. Properties where you are a Full or Restricted user show "Owner needed" instead of the button: only owners can add other owners, which step 3 requires. For a client's site, ask the client to make you an owner of the property, or to sign in and do step 3 themselves.

Step 3: give the indexing account Owner access

Submissions go to Google's Indexing API, and Google only accepts a notification from a service account that is an Owner of a Search Console property covering the URL. Not Full, not Restricted: Owner. TurboIndex gives each site such a service account, an address ending in iam.gserviceaccount.com, and the wizard offers three ways to make it an owner:

1. One click. Google asks for one more permission, to manage the list of sites you control, and TurboIndex uses it once to add the account to the property's owner list. This only works if you verified the property yourself (DNS record, HTML file, meta tag). Owners who were added by someone else are sent to the manual path.
2. In Search Console, by hand. Copy the email the wizard shows, open Settings, Users and permissions, click Add user, paste the email, change the permission from Full to Owner, click Add, then click Verify access back in the wizard. About two minutes, and no extra permission for TurboIndex. This is also the path to send to a client who owns the property.
3. Your own Google Cloud key. The service account lives in your own project, so the daily quota of 200 is yours alone and you can delete the key or the project at any time. Either upload a JSON key you created yourself, or choose Set it up for me and let the wizard create the project, enable the APIs, create the service account and key, and add the owner in your account.

All three end with the same check: TurboIndex asks Google whether the account owns a property that covers the site. When it does, the site switches from "Setup needed" to active and the work begins. If the check fails, the wizard tells you which of the usual causes it is: added as Full instead of Owner, added to a different property, a typo in the email, or Google needing another minute to notice the new owner.

The first hour

Once access is verified, this happens in order, without you doing anything:

Sitemaps are read. TurboIndex fetches the sitemaps submitted in Search Console. If there are none, it looks for Sitemap: lines in robots.txt and then at /sitemap.xml. Sitemap index files are followed. Every URL found appears in the list with the status Found, usually within a minute or two; the Sitemaps tab shows each file, its URL count and when it was last read. Sitemaps are re-read every six hours, so new pages and changed lastmod dates are picked up on their own. Pages that are in no sitemap can be pasted by hand.

Pages are checked by TurboIndexBot. Before a URL can be submitted, TurboIndexBot fetches it and looks at the status code, the redirect chain, the robots meta tag, the X-Robots-Tag header, the canonical link and signs of a soft 404. A page that answers 404 or 410, redirects, carries noindex or points its canonical at another URL is never sent to Google, because the submission would be wasted; it is shown as Blocked with the reason. A page that answers with a server error or times out is retried later. A page that answers 403 or 429 is sent anyway but flagged, because bot protection often blocks TurboIndexBot while letting Googlebot through. The details, including how to allow the bot in a firewall, are in how TurboIndex checks pages before submitting, and the bot itself is described at /bot.

First inspections. TurboIndex asks Google's URL Inspection API for the status of each URL. Google allows 2,000 inspections per property per day, so a site with 500 pages is checked the same day and a site with 10,000 pages takes five days for the first full pass. Pages Google confirms as indexed become Indexed. Pages Google knows but has not indexed become Not indexed, with Google's own words in the "Google says" column. Pages Google has never seen stay in the queue.

First submissions. Pages that are not indexed and passed the check go to the Indexing API, newest and never-submitted first, as many a day as your plan sends: 20 on the free plan, up to 200 for one site on the paid plans (Google's default quota per project). The count starts again at midnight Pacific time. Each one becomes Submitted. If you turn on IndexNow in the site's settings and host the key file it gives you, the same URLs are also sent to Bing, Yandex, Naver, Seznam and Yep.

Reading the dashboard

The site page starts with one figure, pages indexed out of pages found, a bar of the lifecycle statuses, and two meters: Google submissions used today and index checks used today. Below it the URL list, filterable by status and by a text search on the URL.

Status	Meaning	What you do
Found	In your sitemap, first check pending	Wait
Queued	Not indexed, waiting for a free slot in the day's quota	Wait, or select it and click Submit first
Submitted	Sent to Google, result checked over the next days	Wait
Indexed	Google confirmed the page is in its index	Nothing
Not indexed	Google knows the page and has not indexed it	Read the reason in "Google says" and fix the page
Blocked	Something stops indexing: noindex, robots.txt, redirect, 404, canonical elsewhere	Fix it, or leave it if it is intended
Error	Google rejected the submission	Open the Activity tab for the response

A submitted page is inspected again after 2, 3, 5, 7 and 14 days. If it is still not indexed after 14 days, it is queued again, at most three times in total, because repetition does not change Google's mind. Indexed pages are rechecked about every 30 days, and if Google drops one you get an email.

Three controls are worth knowing on day one: Run now on the site page starts a round of index checks and a round of submissions without waiting for the schedule (Read sitemaps now in the Sitemaps tab does the same for the sitemaps); the checkbox next to each URL with Submit first puts a page at the front of the queue; and Never submit keeps a page out of submissions for good.

When pages stay not indexed

After a week or two most new sites split into three groups.

Indexed. Keep publishing and keep the sitemap accurate.

Not indexed with "Crawled - currently not indexed". Google fetched the page and chose not to keep it. Resubmitting does nothing here; the content is the problem. Thin pages, near-duplicates of other pages (yours or someone else's), pages with no internal links, and page types that exist in the hundreds with only the city name changing are the usual reasons. The fixes are in Crawled - currently not indexed.

Not indexed with "Discovered - currently not indexed". Google knows the URL and has not fetched it. On a brand new site this is normal for a couple of weeks. If it lasts longer, the site needs more internal links from pages that are crawled, and fewer low-value URLs in the sitemap competing for Google's attention.

Blocked. Open the reason. A redirect means the sitemap lists an old URL; put the final URL in the sitemap. A noindex means a plugin setting or a template rule; the indexability checker shows where the directive sits. A canonical pointing elsewhere means Google will index that other URL, which is often correct.

Two things not to do: do not add a second account to double the quota (Google calls that abuse and can revoke access), and do not read "Accepted" in the Activity tab as "indexed". Accepted means Google received the request.

What to expect on timing

A submission usually leads to a crawl within days, often sooner. Indexing, if it happens, follows that crawl. For a large site the first inspection pass alone takes days, and the trend chart on the site page is the honest view of progress. Google's own statements on timing are collected in how long does Google take to index.

Google supports the Indexing API officially for job posting and livestream pages. It does trigger crawls for other pages today, and TurboIndex uses it within Google's default quota, one project per site, but that could change, which is why the sitemap, the index checks and IndexNow run regardless.