SEO-Safe Changes

New Pages Missing From Google? Check Discovery Before SEO

Rows of worn paper folders with handwritten tabs in a wooden filing drawer
Who: Owner Effort: typically 1-3 hours for initial checks Cost: free for owner checks; typically CAD 300-1,500 for technical fixes
Give important pages clear internal links and an accurate sitemap, then use Search Console to identify what is stopping Google from indexing them. Neither a sitemap nor an IndexNow notification guarantees indexing or a deadline. First inspect one missing page and record its indexing reason before changing anything.

You published a service page, sent the link to customers, and waited. It opens normally in your browser, but searching Google does not show it. A vendor suggests an indexing package; another says to install an SEO plugin. Neither has explained what is actually wrong.

Start by separating three jobs: helping a search engine discover a URL, letting it crawl the page, and giving it a reason to include that page in its index. This guide explains the checks an owner can do and the evidence to hand a developer. For the broader maintenance plan, keep our website upgrade guides alongside your findings.

1. Find out whether discovery is really the problem

Discovery means the engine knows an address exists. Crawling means it fetches the content. Indexing means it processes that content and chooses whether to include it. Ranking comes later: an indexed page can still appear far below the results you check.

As of 2026, Google's recrawl guidance says crawling can take a few days to a few weeks. It explicitly says a request does not guarantee instant inclusion, or inclusion at all. That makes “indexed in hours” an unsuitable acceptance condition for a contractor.

Use Search Console's URL Inspection tool for one exact address, including its preferred HTTPS hostname. Looking for your page with a normal search is a weaker test: results vary, and an absent result does not tell you the cause. Search Console provides Google's recorded status, while its live test checks current accessibility; passing the live test does not mean the page is indexed.

Finding What it suggests First useful action
Google does not know the URL Discovery may be missing Add a relevant internal link and check the sitemap
Discovered, currently not indexed URL is known; crawling is pending Check accessibility and wait before repeated changes
Crawled, currently not indexed Discovery already worked Review useful content, duplication and canonical signals
Excluded by noindex Page asks to stay out of results Confirm intent before removing the directive
Duplicate with another canonical Google associates it with another page Check whether the chosen page is the right one
Server error or not found Fetching the intended page failed Fix the response or use the correct final URL

Do not remove a deliberate exclusion from a private, test or thank-you page. First decide whether that page belongs in public search at all.

2. Make the sitemap describe the public site

A sitemap is a list of addresses you want search engines to discover. It is particularly useful after a launch or migration, or when some pages have few incoming links. Google's sitemap overview also explains that a small, comprehensively linked site may not need one for discovery. A sitemap is useful housekeeping, rather than a substitute for navigation.

Ask your platform which sitemap it already generates before adding another plugin. Open that address and look for your new page's final URL. Include public pages that should appear in search; leave out redirects, missing pages, deliberately excluded pages and alternate copies. The preferred address is the canonical URL: the version you want treated as the main page.

As of 2026, Google's sitemap instructions recommend listing canonical URLs and using accurate last-modified dates. Do not stamp every page with today's date whenever the site builds. That date should reflect a significant page update, rather than a routine deployment.

For a small site, one platform-generated sitemap is typically easier to maintain than a manually edited file. The case against installing a separate sitemap tool is simple: duplicate generators can disagree and create another maintenance task. Use an extra tool only when the existing platform cannot produce an accurate list.

If a redesign changed addresses, finish the URL change and redirect checklist first. Submitting the old URLs again will not repair missing redirects or tell Google which new page is the replacement.

3. Run a focused Search Console check

Search Console is useful because it reports how Google sees your site. Its limitation is equally relevant: reports can lag behind the live site, and the tool cannot force an indexing decision. Record dates so you can distinguish an old report from an unresolved defect.

  1. Confirm you have access to the Search Console property covering the exact hostname. Ask the domain owner for access if necessary; avoid sharing an administrator's password.
  2. Inspect the missing page's complete URL. Save the reported reason, last crawl date if available, and Google's selected canonical.
  3. Open the page without being logged into your CMS. Confirm visitors can read its main content without a password or an error screen.
  4. Run the live inspection test. If it reports a block, give that specific finding to the person maintaining the site.
  5. Check that at least one relevant public page links to it. A service category or related guide is a better route than hiding it in an unrelated footer list.
  6. Submit the accurate sitemap in the Sitemaps report. For one important new or repaired URL, request indexing after the checks pass.
  7. Revisit your notes after roughly a week, then investigate the stated reason if it persists. This is a review interval, not a promise that indexing should finish then.

As of 2026, Google says requesting a recrawl repeatedly for the same URL does not make it happen faster. Spend that time improving an unclear service page or fixing the recorded error instead.

4. Use IndexNow for notifications, with realistic expectations

IndexNow lets a site notify participating search engines when URLs are added, changed or deleted. Its official documentation describes ownership verification through a key file and submission of changed addresses. As of 2026, an HTTP 200 response means the engine received the notification; it does not mean the page entered the index.

The practical owner question is whether your CMS or deployment already handles this. Ask which events trigger a notification and how a failed submission is recorded. Changed public pages should be submitted after they are reachable, including when a scheduled publication actually opens. Sending a future article before release creates an avoidable mismatch.

The case for IndexNow is timely notification with little ongoing effort once automated. The case against adding it immediately is that it cannot cure a blocked page, poor content or a broken canonical. Its FAQ confirms that submission does not guarantee indexing. Resolve those defects before paying for another integration.

For ordinary pages, as of 2026, Google's documented submission workflow remains sitemaps and URL Inspection. Treat IndexNow as an additional channel for participating engines. It also cannot guarantee citations in AI answers; our small-site AI search guide explains that separate decision.

5. Pay for a fix you can verify

Initial owner checks typically take 1-3 hours. For a small Canadian business site, budget typically CAD 300-1,500 for a bounded technical fix such as correcting sitemap output, an accidental exclusion or canonical templates. These are planning allowances, not supplier quotes; content rewriting and a wider migration need separate scope.

A useful brief names the URL, the observed problem, the intended behaviour and the evidence required afterward. For example: “This public service page is accidentally marked noindex. Remove that directive, confirm its preferred URL and add it to the existing sitemap.” The developer can prove those changes without promising search traffic.

Track important pages in a simple list: address, publish date, inspection reason, action taken and next review date. If an indexed page receives few visits, switch the investigation to demand, relevance and how clearly it answers the searcher's question. Repeated submission solves neither an unhelpful page nor a weak offer.

— Editorial team. Facts current as of 2026; we revise guides when the ground shifts.

Frequently Asked Questions

How long does Google take to index a new page?

As of 2026, Google says crawling can take a few days to a few weeks; that is not an indexing deadline. Some pages may never be indexed, so use Search Console to distinguish a technical blocker from an indexing decision.

Does IndexNow submit my pages to Google?

IndexNow notifies participating search engines of changed URLs. As of 2026, Google's documented routes for ordinary web pages are sitemap submission and URL Inspection; keep using those rather than treating IndexNow as a Google submission service.

Should I buy a service that promises instant indexing?

Pay for a diagnosed fix with clear acceptance criteria, such as removing an accidental noindex directive. A third party cannot guarantee Google's indexing decision, so an instant-indexing promise is not a sound purchase criterion.