Reading SEO reports

Your New Page Has No Obvious Internal Links: Where Should You Add One?

Find a useful place for an internal link and check whether visitors and Google can follow it.

You published a useful page. It appears in your sitemap, and you can open it by typing its address. But a visitor browsing your site has no obvious way to reach it. Where should the first link go, and how can you tell whether Google can follow it?

Start with a page that already helps the kind of reader your new page is for. A relevant link there can give people a route to the new page and give search engines another way to discover it. It does not guarantee crawling, indexing or a particular ranking. Place the link where it helps the reader continue, check that it reaches the intended URL, and give Google time to process the change.

First, check whether the page already has a route

Open your site as a visitor, preferably in a private browser window if the page is meant to be public. Starting from a relevant category, guide or product page, try to reach the new URL without typing it into the address bar. Record the page you started from and the link text you used.

If you cannot find a route, that is a reason to check further, not proof that the page has no internal links anywhere. A search box, a related-content block, an older article or a link added by your CMS may provide another path. Conversely, a link visible only after signing in may not be a public route.

For a second view, open the Links report in Google Search Console and look under Internal links → Top linked pages → More for the destination URL. Select it to see examples of pages Google has found linking to it. This report is a sample of links discovered over time, so a destination absent from the report or a new link that has not appeared yet is not conclusive evidence that no link exists. Google explains the report's scope in its Links report documentation.

A sitemap can list a page without creating a navigable link on your site. It is useful for sharing preferred URLs, but a sitemap does not guarantee crawling or indexing. Keep the sitemap entry if the page belongs there; also give readers a route where it makes sense.

Choose the source page by the reader's next question

A link works best where the destination helps someone continue a task. For example, imagine a small bakery publishes a page explaining how to order a custom cake. A paragraph on its existing cake menu is a natural place to link: a visitor considering a cake may want to know lead times, serving sizes and how to order. A link buried in an unrelated privacy policy would be much less useful to that reader.

Use your actual content, not this fictional example, to make the decision:

  1. Name the destination's purpose in one sentence. What will a visitor find or do there?
  2. Find an existing public page whose reader is likely to need that next step. A related service page, product category or explanatory article can all be suitable.
  3. Add the link within the relevant sentence or section. Keep the surrounding explanation accurate even if the visitor never clicks.
  4. If the destination is genuinely important to the site's main journeys, consider whether a category page or navigation item should also lead to it. A footer link on every page is not automatically a better answer than one well-placed contextual link.

You do not need to force every article to link to every other article. Google recommends making important pages reachable from another relevant page and using link text that helps readers understand the destination; it does not prescribe a magic number of links. See Google's link best practices.

Make the link clear and followable

Write link text that describes the destination in context. “See custom cake ordering details” gives a reader a better expectation than “click here.” It does not have to repeat a target keyword exactly, and it should not promise information the destination does not provide.

If you edit HTML, a normal link can look like this:

<a href="/custom-cakes/order">See custom cake ordering details</a>

The path above is an example, not a page on your site. Your own link should point to the actual destination. In a CMS, use its ordinary link control and paste or select that URL. Clicking the finished link should lead to the page you intend, not a login screen, a missing page or an unnecessary redirect chain.

A control that merely runs JavaScript when clicked may work for a person but is harder for crawlers to interpret than an actual <a> element with a usable href. JavaScript can also add valid links: inspect the rendered page rather than assuming that every dynamically inserted link is invisible. Google's link documentation gives examples of both patterns. If your builder manages the markup, ask its support how to create a normal crawlable link rather than inserting code you cannot maintain.

Check the destination separately

A good link to the wrong version of a page is still a frustrating route. Open the destination in a private window and confirm the content is available to the intended visitor. If clicking the link changes the address, check whether the redirect is intentional. For duplicate versions of substantially the same page, use the preferred URL consistently; a canonical annotation is a signal to Google, not a command that guarantees its selection. Google's canonicalization guide explains the distinction.

Then inspect the destination in Search Console. The indexed result describes Google's stored information; a live test checks the current page but does not itself mean that Google has indexed the new version. If the report identifies a restriction or another reason the page is not indexed, investigate that reason rather than assuming the internal link is the only issue. For example, an accidental noindex needs its own correction. Our guide to finding the source of a noindex directive walks through that check.

Recheck without mistaking one signal for another

After publishing the link, open the source page again and follow it. On the source URL, Search Console's URL Inspection tool can help you examine the rendered HTML when the link is added by JavaScript. Search for the destination path in the rendered output and check that the link points where you intended. This tests what the tool can see in that test; it is not a promise of when Google will revisit or index the destination.

Keep a short record: source URL, destination URL, link text, date published and what you observed on the recheck. Later, revisit the Links report and the destination's indexing status. The Links report can lag and is sampled. If the page remains unindexed, compare its reported reason, public availability, preferred URL and usefulness before deciding what to change next. Repeatedly submitting an unchanged sitemap or requesting indexing is not a substitute for diagnosing a real issue, and neither action guarantees a result. See Google's recrawl guidance.

If you want a separate starting check on your own site's homepage, SEOHabit's website SEO checker offers a limited homepage check after sign-up. Ownership verification is needed for ongoing checks. It can flag issues worth investigating; you or your own tools make and verify any changes on your site.