SOP: automate internal links without orphans
Wire the mesh at generation time, not as an afterthought.
— Step 1 (Dev): Every generated page must link to its parent hub and its sibling category index. Gate: zero outbound contextual links → fail.
— Step 2 (Dev): Inject 4–8 related-entity links chosen by a deterministic rule (shared attribute, nearest neighbor), not random. Gate: same input → same links.
— Step 3 (SEO): Cap links from any single hub at a sane number so equity isn't diluted. Gate: hub linking to 2,000 children → paginate or cluster.
— Step 4 (Dev): Anchor text pulls the target's real H1 token, not 'click here' and not the exact head keyword every time.
— Step 5 (Ops): Run an orphan scan after each batch. Gate: any URL with zero internal inlinks → block from sitemap until linked.
Guardrail: reciprocal links between siblings, one-way links up to hubs.
Ship gate: don't publish until all boxes are checked.
Wire the mesh at generation time, not as an afterthought.
— Step 1 (Dev): Every generated page must link to its parent hub and its sibling category index. Gate: zero outbound contextual links → fail.
— Step 2 (Dev): Inject 4–8 related-entity links chosen by a deterministic rule (shared attribute, nearest neighbor), not random. Gate: same input → same links.
— Step 3 (SEO): Cap links from any single hub at a sane number so equity isn't diluted. Gate: hub linking to 2,000 children → paginate or cluster.
— Step 4 (Dev): Anchor text pulls the target's real H1 token, not 'click here' and not the exact head keyword every time.
— Step 5 (Ops): Run an orphan scan after each batch. Gate: any URL with zero internal inlinks → block from sitemap until linked.
Guardrail: reciprocal links between siblings, one-way links up to hubs.
Ship gate: don't publish until all boxes are checked.
Mistake: a URL pattern that changes when the source data changes
If the slug is built from a mutable field — a company's display name, a re-orderable category — then a rename silently changes the URL, orphaning the old one and creating a duplicate. At scale this manufactures thousands of soft-404s.
Stable-URL SOP:
— Step 1. Owner: dev. Slugs derive from an immutable id or a frozen slug column, never from a field users can edit.
— Step 2. Owner: dev. On any name change, keep the original slug and 301 only via an explicit, logged redirect — never by re-slugging in place.
— Step 3. Owner: SEO. Diff this build's URL set against last build's. Gate: any URL that disappeared must have a 301, or the build fails.
— Step 4. Owner: data. Store slug_history so old URLs always resolve.
Guardrail: URLs are append-only; you add and redirect, you never silently mutate.
Ship gate: don't publish until all boxes are checked.
If the slug is built from a mutable field — a company's display name, a re-orderable category — then a rename silently changes the URL, orphaning the old one and creating a duplicate. At scale this manufactures thousands of soft-404s.
Stable-URL SOP:
— Step 1. Owner: dev. Slugs derive from an immutable id or a frozen slug column, never from a field users can edit.
— Step 2. Owner: dev. On any name change, keep the original slug and 301 only via an explicit, logged redirect — never by re-slugging in place.
— Step 3. Owner: SEO. Diff this build's URL set against last build's. Gate: any URL that disappeared must have a 301, or the build fails.
— Step 4. Owner: data. Store slug_history so old URLs always resolve.
Guardrail: URLs are append-only; you add and redirect, you never silently mutate.
Ship gate: don't publish until all boxes are checked.