Step by step
How to submit a new page for indexing in Google Search Console
Basic · 15 minutes of work · 2 minute read · Updated October 31, 2026
A new page or article will not show up in Google instantly. You can, however, help Google's crawlers find it sooner. This guide walks through the whole process in Google Search Console.
Before you start
- The site must be publicly accessible (no password, no crawler block).
- You need a Google account and access to your domain or site files.
- Make sure
robots.txthas noDisallow: /rule and the page has nonoindextag.
Step 1. Add your site to Search Console
- Go to search.google.com/search-console and sign in.
- Click "Add property" and choose Domain (covers all subdomains and protocols) or URL prefix.
- For a domain, add the TXT record Google gives you in your DNS settings. For a prefix, you can use an HTML file or a meta tag.
- Click "Verify". DNS changes can take a while to propagate.
Step 2. Submit your sitemap
- In the menu choose Sitemaps.
- Enter the sitemap address, usually
sitemap.xml, and click "Submit". - Check that the status says "Success" and the discovered URL count looks right.
A sitemap does not guarantee indexing, but it gives Google a full list of URLs to check.
Step 3. Request indexing for a specific page
- Paste the full URL of the new page into the search bar at the top.
- Wait for the inspection result. If you see "URL is not on Google", click Request indexing.
- If you see "URL is on Google", you do not need to do anything else.
There is a daily quota for these requests, so spend it on your most important URLs: new services, articles and guides.
Step 4. Add internal links
Crawlers find pages fastest when an already indexed page links to them. Link the new URL from your home page, the article list or a related service page.
Step 5. Check the result after a few days
Return to the Pages report in Search Console. You will see which URLs are indexed and which show "Discovered, currently not indexed" or "Crawled, currently not indexed". These two statuses often point to low-value or duplicated content rather than a technical fault.
Common problems
- A noindex tag left over from testing.
- A canonical pointing to a different URL.
- Redirects and 404 errors in the sitemap.
- Thin content or content very similar to other pages.
Table of contents
Frequently asked questions
Services related to this guide
Keep reading
Basic · 30 minutes of work
Jak przetestować formularz kontaktowy na stronie, żeby żadne zapytanie nie ginęło
Formularz, który wygląda dobrze, ale gubi wiadomości, kosztuje klientów. Sprawdź go w 30 minut: wysyłka, spam, powiadomienia i komunikaty błędów.
Basic · 120 minutes of work
Jak sprawdzić i ujednolicić dane firmy (NAP) w internecie w dwie godziny
Różne adresy i telefony w katalogach mylą Google i klientów. Krok po kroku: spis miejsc, wzorcowe dane, poprawki i kontrola.
Basic · 30 minutes of work
How to back up a business website and confirm it can be restored
A backup you have never tested is hope, not protection. How to set up website backups and periodically confirm they work.
Would you rather have someone do it for you?
Describe what you want to achieve in a brief. We reply with specifics, no sales call.
Send a brief