How to Add Internal Links to New Posts So Google Finds Them
You hit Publish, the post shows up in your XML sitemap, and then nothing happens for weeks. No page on your site links to it, so Google has no road to follow from the pages it already knows.
Publishing feels like the finish line, and after hours of research and drafting, that is a fair assumption. But a post that exists only in the sitemap has no crawl path from already-indexed pages. Adding internal links to new posts on publish day is the most reliable way to get Google to discover new posts without leaving it to chance.
This guide gives you a repeatable publish-day sequence. You will build a simple internal links map, follow five linking steps, and finish with an orphan check.
That last check matters more than it looks. Most teams skip the final step, and a post can look linked to you while Google still treats it as an orphan.
Google finds new posts faster when already-indexed pages link to them. A sitemap entry announces that a URL exists. An internal link gives Google a path to reach it.
How Do Internal Links Help Google Find New Blog Posts?
Internal links help Google find new posts because Googlebot, Google's crawler, follows links from pages it already crawls to discover URLs it has not seen. A link from an indexed pillar or sibling post creates a crawl path from familiar pages to the new URL. A crawl path is the chain of links a crawler follows to reach a page.
Without that link, the post depends on the sitemap alone. It then competes for whatever crawl budget Google gives your site for new URLs.
Think of your site as a town and links as roads. A post with no inbound links is a house with a registered address but no street leading to it.
An orphan page is a published URL that no other page on the same site links to. A pillar page is the broad, central article on a topic that links to every narrower post in its cluster.
Placement also matters. Crawl depth is the number of clicks from the homepage to a page. A link on page 12 of a paginated archive is a weaker discovery path than a link from a pillar page.
| Method | What it does | What it doesn't do |
|---|---|---|
| XML sitemap | Tells Google the URL exists | Supply a crawl path or topical context |
| Indexing request | Asks Google to crawl one URL | Connect the page to the rest of your site |
| Internal link | Supplies a crawl path and topical context through anchor text | Guarantee indexing on its own |
Before you start, build an internal links map. This is a spreadsheet with five columns: URL, topic, pillar, sibling posts, and target anchors. You can build it by hand from your sitemap, or let BloGoose generate it when it crawls your site during setup.
Worked example: A post on recipe schema sits only in the sitemap. Once the recipe SEO pillar links to it, the post gets its first crawl path from a page Google already indexes.
How to Link a New Post on Publish Day in 5 Steps
To link a new post on publish day, connect it to its pillar and to related sibling posts, then link it back up to the pillar. This Publish-Day Link Sequence takes about 20 minutes per post:
- Link from the pillar page.
- Add two to three sibling links.
- Link the new post up to its pillar.
- Write descriptive anchor text.
- Schedule a revisit.
Prerequisites: your internal links map and editor access in your CMS.
Step 1: Link From the Pillar Page (5 minutes)
Open the pillar listed in the map's pillar column. Find the paragraph that matches the new post's topic, add a link in that paragraph, and click Update.
The new URL is now part of the topic cluster. It also has a crawl path from an indexed page.
Step 2: Add Two to Three Sibling Links (8 minutes)
Filter the map's topic column for posts that share the new post's topic. The selection rule is one pillar link plus two to three sibling links, all chosen from the map.
Worked example: A new post on recipe schema errors is tagged "structured data." The map lists three siblings with that tag: recipe schema basics, FAQ schema, and testing rich results. Link from the first and third, which discuss errors directly.
Step 3: Link the New Post Up to Its Pillar (2 minutes)
Add a link to the pillar in the new post's first section. Teams skip this upward link more often than any other step.
Breadcrumb navigation adds a second structural upward link. Check that the trail reads Home, then the pillar category, then the new post.
Step 4: Write Descriptive Anchor Text (3 minutes)
Choose anchor text that describes the target page, such as "fixing recipe schema errors," not "click here." Each anchor should read like a short label for the page it points to.
Pro tip: Vary the anchors across sibling links instead of repeating the exact keyword. For example, use one close variant, one question phrase, and one partial match.
Step 5: Schedule a Revisit (2 minutes)
Add a calendar reminder, because internal links need upkeep. Revisit the post when any of these happen:
- A new sibling post is published.
- The pillar is updated while refreshing older content.
- The post is still not indexed.
Keeping the map current by hand is where this sequence usually breaks down. BloGoose builds the internal links map from your sitemap automatically, so every new draft starts with its pillar and siblings already identified.
Once the links are in place, confirm that Google sees them too, which starts with how to check the new post is not orphaned.
How to Check the New Post Is Not Orphaned
An orphan page is a URL listed in your sitemap that no crawlable internal link points to. To confirm your new post isn't one, crawl your site from the homepage and check that the post's URL shows up in the results.
Think of it as a book listed in the library catalog that sits on no shelf. The record exists, but nobody browsing the aisles will ever find it.
To run an orphan check, crawl your site from the homepage with a tool that follows HTML links, export the URLs it reached, and compare that list against every URL in your XML sitemap. Any URL that appears in the sitemap but is missing from the crawl is an orphan, because Google can reach it only through the sitemap and never through your internal links. For a new post, search the crawl export for its exact URL, and if it's absent, at least one of the links you added on publish day isn't crawlable.
If you linked the post and it's still orphaned, the link probably isn't a plain HTML anchor. A plain HTML anchor is an a tag with an href attribute that crawlers can follow.
| Symptom | Cause | Fix |
|---|---|---|
| The related-posts widget shows the post, but the crawl misses it | The widget's links are rendered only by JavaScript | Add an in-body HTML link from a sibling post. See JavaScript-rendered links. |
| The link is visible, but the crawler ignores it | nofollow is set on the internal link | Remove nofollow from the link |
| The post is linked only from deep archive pages | Deep paginated archives | Add a link from the pillar page |
| The plugin reports a link, but the page source shows none | The plugin outputs no HTML anchor | Add the link manually in the post body |
WordPress auto-linking plugins have a related limit. They can insert irrelevant anchors or over-link a page, so view the page source and confirm what they actually output.
Internal Linking FAQ for New Posts
These answers cover the questions people most often ask after publishing and linking a new post.
How many internal links should a new blog post get?
Start with three to four inbound links. Use the pillar-plus-siblings rule: one link from the topic's pillar page and two or three from closely related sibling posts. Place each link in body copy with descriptive anchor text. Treat this as a practical starting point, not a magic number.
Can a WordPress plugin add internal links automatically?
Yes, but plugins don't judge whether an anchor is relevant. They match keywords, so they can link the wrong phrase or over-link a single page. Review each post's output before or right after publishing, and remove links that don't help a reader.
Do sidebar and menu links count as much as in-body links?
No. Sidebar and menu links create crawl paths, but in-body links carry the topical context. A contextual link inside a related paragraph tells Google what the new post covers. A navigation link mostly tells Google that the post exists.
Why isn't my new post indexed after I added internal links?
Internal links help Google discover a page, but they don't guarantee indexing. First, run the orphan check to confirm your links are crawlable HTML anchors. Then check that the post isn't blocked by a noindex tag. Finally, give Google time to recrawl the pages that link to the new post.
Make Linking Part of Publishing, Not Cleanup
New posts get found fastest when their internal links ship with the post, not weeks later during an audit. A sitemap tells Google a page exists. Links tell Google that the page matters and where it fits.
Before your next post goes live, run this sequence:
- Open your internal links map.
- Place the pillar and sibling links.
- Add the upward link to the pillar.
- Run the orphan check.
- Set a revisit date to add links from newer posts.
As a next step, let BloGoose build the internal links map from your sitemap and place links in your next post before it publishes to WordPress. For the rest of the discovery toolkit, read how to get Google to discover new posts. Each post you publish already connected makes the next one easier for Google to find.