# Internal linking and search

For each indexable page record its visitor question, canonical path, parent page, related destination and next action. A page should be reachable through ordinary HTML links from a relevant page. The sitemap is an additional discovery path.

| From | Link to | Example anchor |
| --- | --- | --- |
| Services overview | Individual service | Site planning |
| Service detail | Decision guide | Prepare your project brief |
| Decision guide | Relevant service | Discuss site planning |
| Verified location | Available service | Site planning services |
| Service detail | Inquiry | Discuss your project |

Use the destination's real path. Link within the paragraph where the reader needs the answer. Keep breadcrumbs on detail pages. On a metal building site the path might be RV carports → sizing guide → clearance worksheet → quote. Publish each link only after the destination exists.

Before launch, crawl from the homepage, identify orphan pages, check descriptive link text and check old WordPress URLs and redirects. Inspect a sample canonical, unique title, description, robots policy and sitemap on the deployed domain. Run npm run qa for local link and metadata checks. Review meaningful inbound links manually.

Prompt: Using the knowledge profile and existing routes, map each published service to its parent, one useful guide and its next action. Report missing destinations; never create a link to a guessed URL.

Reference: https://developers.google.com/search/docs/crawling-indexing/links-crawlable
