Reference publishing guides

Find and repair orphan reference pages in a static Astro site

Audit both the generated route set and the links that lead to it. A successfully built article can still lack a useful incoming path. Give each maintained reference a relevant directory or hub link, then verify that the built page and its navigation agree.

Updated 815 words · 4 min read2 sources · scope listed below
Reading the sources

This reference uses the specific documents linked in the article and listed below. Check their scope, publication dates and the statements they support.

Keep route generation and navigation separate

Astro's routing documentation explains how getStaticPaths() enumerates dynamic routes for a static build. It also uses ordinary HTML anchors for navigation. Generating a route and linking to that route are therefore separate pieces of a reference site's publication workflow.

Start from a canonical inventory containing route, title, content kind and publication status. Exclude deliberately unpublished drafts from the public-link requirement. Keep retired aliases in a redirect inventory so they cannot be confused with maintained articles that need new incoming links.

Build a small link graph

Treat each canonical HTML route as a node. For every built page, extract local anchor destinations and resolve relative paths against that page's address. Separate a destination's path from any fragment so an in-page contents link does not count as another article discovering itself.

Count incoming links from different pages. A self-link is not an incoming reading path. Record the source route, visible label and link location alongside each destination so a failing check produces an actionable list rather than just a number.

Separate broad coverage from useful context

An exhaustive sitemap can make every page technically linked while the animal hubs and subject directories remain incomplete. Report sitemap coverage and contextual incoming links separately. The second view asks whether a reader can reach the article through a relevant task or browsing category.

Google's link guidance describes crawlable anchors with href and useful descriptive link text. Use those elements in the rendered page. A search result that appears only after typing a precise term should supplement the static browsing path, not be its sole planned entry point.

Reproduce a pagination failure

Imagine a fictional category with sixty maintained articles and forty-eight cards per index page. The first page is linked from the library, but its “next” control is missing. The remaining twelve cards exist on a generated second page that has no incoming link.

The repair is not twelve arbitrary links from the homepage. Restore the category's pagination, ensure both pages use the same sorted member set and compare their combined destinations with the category inventory. Also check that the second page links back and that list totals describe the full category rather than the current slice.

Repair the relationship that failed

If a directory omitted a valid member, correct its member selection. If a category name is wrong, repair the classification before adding links. If a retired alias appears in a card, update that card to the maintained destination while preserving the alias redirect for older links.

Use animal hubs carefully. An article's presence in the inventory does not establish an animal relationship. Add condition links through a reviewed editorial selection rather than guessing host susceptibility from title fragments. A structural navigation repair should not silently create a scientific claim.

Check the build people will receive

Inspect final HTML after rendering, since templates can omit data that looked correct in the source object. Confirm that linked paths resolve in the deployment's trailing-slash and base-path configuration. Follow representative category, pagination and article journeys without using local development shortcuts.

Retain a concise release check: maintained routes missing from output, local links without destinations, canonical articles without non-self incoming links, and contextual orphans hidden by the sitemap. A passing graph check shows navigation consistency; it does not guarantee search indexing or article quality. Pair it with the article-versus-record guide and a direct reading inspection of the destinations.

Questions for a navigation audit

Does sitemap inclusion mean a page has a useful reading path?

Report it separately from relevant hub and directory links. The sitemap can provide broad coverage while a category selection or pagination defect still hides the page from ordinary browsing.

Should every orphan be linked from the homepage?

Repair the relationship that failed. A missing category member belongs in the relevant maintained list; a pagination gap needs a connected page sequence. Arbitrary homepage links can hide the structural defect without helping a reader understand the library.

Does a passing link graph establish scientific relevance?

It verifies the relationships represented by its checks. Host or condition links still need a supported editorial basis, and a resolved route can lead to an inadequate article. Inspect representative reading journeys alongside the graph report.

In a second fictional audit, the extractor counts fragment links within each article as incoming links. Every route appears connected even though none has a link from another page. Removing self-links from the incoming count exposes the actual orphans. Preserve the source route and anchor label in the report so the repair can be reviewed. A numerical count is useful only when its definition reflects the navigation question being asked.

Cite this reference

LivestockDefense. “Find and repair orphan reference pages in a static Astro site.” Updated 2026-11-03. https://livestockdefense.com/guides/preventing-orphan-disease-pages-in-a-static-astro-build/

Add the date you accessed the page. This identifies the current reference; keep a permitted saved copy if your work depends on its exact wording. A citation alone does not establish support for a claim.

How to cite a page and its revision ↗

Sources & boundaries

Read the evidence in context.

These documents support the statements identified in this reference. Check their scope and dates when deciding whether they answer your question.

  1. Google Search Central: Link best practices for Google

    Source update: 2025-12-10. Most recent check: 2026-10-29.

    Document scope and recorded checks

    Technical guidance on crawlable anchor links, descriptive link text and internal navigation; no clinical claims. Crawlable anchor links with href, descriptive link text and relevant internal links; no clinical claims.

    Entries retain the date and scope of each recorded inspection.

    • 2026-10-29 — Crawlable anchor links with href, descriptive link text and relevant internal links; no clinical claims.

      Exact official documentation inspected for the bounded publication or technical statements assigned to it; no clinical verification

    • 2026-10-28 — Technical guidance on crawlable anchor links, descriptive link text and internal navigation; no clinical claims.

      Exact document inspected for the bounded statements assigned to it

  2. Astro documentation: Routing

    Source update: Not provided. Most recent check: 2026-10-29.

    Static dynamic routes use getStaticPaths to enumerate build-time paths; ordinary HTML anchor elements connect routes. Not a guarantee of crawling or indexing.

Full source register ↗