GUIDE INTO PLACE • BEGINNER SEO
Why Is My New Website Not Showing on Google? A Beginner’s Checklist
Seven practical checks to help you find the problem and choose your next step.
You have launched your website, typed its name into Google and found nothing. It can feel as though something has gone badly wrong.
Often, the explanation is simpler: Google has not discovered the site yet, has not indexed the page, or has indexed it but does not consider it the best result for the words you searched.
Those are three different situations:
- Discovery: Google needs to find the URL.
- Indexing: Google needs to process the page and decide whether to store it in its search index.
- Ranking: An indexed page still needs to compete with other pages for a particular search.
The right fix depends on which stage is causing the problem. Work through the following checks in order instead of repeatedly submitting the same page.
1. Confirm that the website is publicly accessible
Open the exact page in a private or incognito browser window. If possible, also open it on a phone using mobile data.
The page should:
- load without requiring a login;
- use the expected public address;
- show the real content rather than a “coming soon” page;
- avoid redirecting to an old or temporary domain; and
- return a working page rather than a 404 or server error.
Google’s technical requirements say a page must be publicly accessible and must not block Googlebot if it is to be indexed normally. If ordinary visitors cannot load the page, solve that problem before looking for an SEO fix.
Check the address left in your browser after the page loads. Use that final address in Search Console and your internal links. If both HTTP and HTTPS, or both www and non-www versions, open separately, ask your host or website administrator to check redirects and canonical settings before changing anything yourself.
Example: Maia launches maiasgarden.co.nz, but visitors are redirected to the temporary address supplied by her hosting company. She should correct the domain and redirect setup first. Requesting indexing for the wrong address will not solve the underlying problem.
2. Check the exact URL in Google Search Console
Google Search Console’s URL Inspection tool is more reliable for troubleshooting one page than repeatedly searching Google for the site name.
Paste the complete URL into URL Inspection, including https:// and the correct ending slash if the site uses one.
You may see a result such as:
- URL is on Google: The page is indexed and eligible to appear, although Google does not guarantee that it will appear for every search.
- URL is not on Google: Open the page-indexing details to find the reason.
- URL is unknown to Google: Google has not discovered or processed the address yet.
The familiar site:example.com search can provide a quick clue, but Google says site: results are not guaranteed to show every indexed URL. Use URL Inspection for the diagnosis.
If Search Console says the page is indexed but you still cannot find it for a broad phrase such as “garden advice,” the issue is more likely ranking than indexing. A new page may be competing with many established pages.
3. Remove accidental WordPress indexing blocks
WordPress includes a setting that asks search engines not to index the site. It is useful while a website is being built, but it can remain enabled by mistake after launch.
In the WordPress dashboard, go to:
Settings → Reading → Search Engine Visibility
For a public website, “Discourage search engines from indexing this site” should normally be unticked. Save changes if you alter it. In standard WordPress, this setting controls a robots meta instruction. Unticking it does not remove a separate noindex set by an SEO plugin or server, and it does not repair a custom robots.txt file.
Also check the page’s SEO settings. Plugins such as Yoast SEO can apply a noindex instruction to an individual page, post type or archive. If the page should appear in search, its setting should allow search engines to show it.
Google explains that a noindex meta tag or HTTP header tells supported search engines not to include the page in results. After removing an accidental noindex, use URL Inspection’s live test. If indexing is now allowed, request indexing once.
Do not make random changes to robots.txt. Google says robots.txt primarily manages crawling; it is not the correct way to guarantee that a web page stays out of search. If a page is blocked by robots.txt, Google cannot crawl it to read a noindex instruction, and the URL may still appear in search if other pages link to it. If your aim is to exclude a page from search, Google needs to be able to crawl it and read its noindex instruction. A noindex is not a privacy control; sensitive content needs proper access restrictions. If Search Console reports a robots restriction on a page you want indexed, identify the exact rule before editing the file.
4. Submit a sitemap and make sure Google can read it
A sitemap lists the URLs that you want search engines to discover. WordPress SEO plugins commonly create one automatically.
Typical sitemap addresses include:
https://example.com/sitemap_index.xml— the usual Yoast SEO sitemap index.https://example.com/wp-sitemap.xml— the native WordPress sitemap index, available since WordPress 5.5 when enabled.
Use the sitemap generated by your active setup. Both addresses do not need to work; an SEO plugin may replace the native WordPress sitemap.
Open your sitemap in a browser. It should load publicly and list the correct website addresses.
In Search Console, open Sitemaps, enter the sitemap address and submit it. Then check the reported status for parsing or access errors.
A sitemap helps Google discover URLs, but it does not guarantee that every submitted page will be crawled, indexed or ranked. Treat it as a discovery aid rather than an approval form.
For a small new website, submit the sitemap once and keep it current. There is no benefit in submitting the unchanged file every day.
5. Link to the new page from another useful page
A page that exists only in the sitemap can still be difficult for visitors—and search engines—to discover in context.
Add a normal internal link from a relevant page that is already part of the website. Use link text that describes what the reader will find.
For example:
- Better: balcony vegetable gardening guide
- Weaker: Click here
Google recommends crawlable links and concise, relevant anchor text. Internal links also help people understand how your pages fit together.
Check that the new page is not an “orphan”: a page with no meaningful links pointing to it. Useful places for internal links include:
- a related article;
- the appropriate Roadmap or resource page;
- a category or topic hub; and
- a short “next step” section.
Do not add dozens of unrelated links. One or two relevant connections are more useful than a footer stuffed with every page on the site.
6. Make the page worth indexing
Technical access is only part of the decision. Google states that indexing is not guaranteed, even when it can crawl a page.
Review the page as a reader:
- Does it answer a clear question or complete a useful task?
- Is the main information original and specific?
- Does the title accurately describe the page?
- Does the page add something beyond a short summary of other websites?
- Is it substantially different from other pages on your own site?
- Can a visitor tell who created it and why they should trust it?
Thin placeholder pages, near-duplicates and pages created mainly to target a phrase may not earn lasting visibility. Google recommends helpful, reliable, people-first content rather than content made primarily to manipulate rankings.
Example: Ben publishes five pages called “Best Beginner Website Tips,” each containing a slightly different 150-word introduction. Combining them into one practical guide with real examples, screenshots and a checklist would create a clearer resource and reduce duplication.
There is no magic word count. The page needs enough information to solve its stated problem without unnecessary padding.
7. Request indexing once, then allow time
After you have fixed any problem, return to URL Inspection. The following live-test sequence is useful for checking your fix; running a separate live test is not a mandatory step before requesting indexing:
- Test the live URL.
- Confirm that the page fetch succeeds.
- Confirm that indexing is allowed.
- Click Request indexing.
Search Console limits how many individual indexing requests you can submit per day. Reserve requests for important new pages or pages where you have fixed a problem. Repeated requests for the same URL will not get it crawled faster.
For many new or updated pages, an accurate sitemap and strong internal linking are the better ongoing method. Google recommends sitemaps for larger groups of new or changed URLs.
Requesting indexing puts the URL into a crawl queue. It does not guarantee immediate inclusion, a ranking position or traffic. Google’s troubleshooting guidance advises allowing at least a week after a sitemap submission or indexing request before assuming that a new page has a problem.
Use that waiting period productively. Check the page on mobile, improve its internal links, add a clear title and description, and begin creating the next genuinely useful page.
What common Search Console messages mean
| Search Console message | Plain-English meaning | Sensible next step |
|---|---|---|
| URL is unknown to Google | Google has not discovered or processed the page | Verify public access and remove unintended indexing blocks; add an internal link and include it in the sitemap, then request indexing if appropriate |
| Discovered – currently not indexed | Google knows the URL but has not crawled it yet | Check access, internal links and server reliability; then allow time |
| Crawled – currently not indexed | Google visited the page but did not index it | Review originality, usefulness, duplication and canonical signals |
Excluded by noindex | The page tells search engines not to index it | Remove noindex only if the page should be public, then retest |
| Blocked by robots.txt | A robots rule prevents normal crawling | Identify the exact rule; change it only if the block is unintended |
| Duplicate; Google chose a different canonical | Google sees another URL as the main version | Check duplicate URLs, redirects and canonical settings |
| Not found (404) | The URL does not return a working page | Restore a page that should exist, correct a broken link, or redirect an old URL only when a relevant replacement exists; otherwise a genuine 404 can remain |
Not every excluded URL needs fixing. Cart, account, filter, duplicate and intentionally private pages often should not appear in search. Focus first on the homepage, Roadmap or service pages, useful articles and other pages that people genuinely need.
A 15-minute launch check
Use this quick routine for a new page:
- Minute 1: Open the page in a private browser window.
- Minutes 2–4: Inspect the exact URL in Search Console.
- Minutes 5–6: Check WordPress and Yoast indexing settings.
- Minutes 7–8: Confirm the page appears in the sitemap.
- Minutes 9–11: Add one relevant internal link.
- Minutes 12–14: Check the title, main heading and usefulness of the content.
- Minute 15: Run the live test and request indexing if appropriate.
Record the date, the Search Console result and any change you made. That prevents repeated submissions and gives you a simple history to review.
Indexing is the first step, not the finish line
Getting a page indexed means it can be considered for Google Search. It does not mean it will immediately rank for a competitive keyword.
Once the page is indexed, focus on the work that helps readers:
- publish genuinely useful content around a clear subject;
- link related pages together;
- keep navigation simple;
- make the website usable on mobile;
- improve slow or confusing pages; and
- review Search Console over time for actual queries and impressions.
Continue with Chapter 6: Grow Your Audience for the broader SEO and audience-building process. GITP’s guide to linking Google Analytics and Search Console explains how the two tools answer different questions.
After Google can access your page, use the free Website Performance Checker to identify practical speed, accessibility and SEO checks. Its automated scores are a starting point; they do not establish whether Google has indexed a page or guarantee rankings.
If you need a structured publishing and promotion plan, see the 30-Day Content & Traffic Action Guide. This is a paid GITP resource; check the current product details before purchasing.
Frequently asked questions
How long does a new website take to appear on Google?
There is no fixed time. Google advises allowing at least a week after submitting a sitemap or requesting indexing before assuming there is a problem. Discovery and indexing can take longer, and indexing is never guaranteed.
Does submitting a sitemap guarantee indexing?
No. A sitemap helps Google discover preferred URLs, but Google does not guarantee that every submitted URL will be crawled or indexed.
Why is my page indexed but not showing for its keyword?
Indexing and ranking are different. An indexed page is eligible to appear, but Google still chooses results according to the query and its ranking systems. Improve the page for the intended reader and evaluate the real queries reported in Search Console.
Should I request indexing every day?
No. Request it after publishing an important page or after fixing a genuine indexing problem. Repeated requests do not guarantee faster inclusion. Maintain a working sitemap and relevant internal links instead.
Should every WordPress page be indexed?
No. Pages such as carts, account screens, internal search results and duplicate archives may have little value in public search. Decide based on whether the page gives searchers a useful destination.