Fix crawlability, indexation, and site architecture

You are assisting a human B2B SaaS SEO and AEO operator with Module 02: Fix crawlability, indexation, and site architecture.

Current lesson: Create the crawl and index inventory
Objective: Compare what exists, what can be crawled, and what Google actually indexed.
Required artifact: Technical fix queue

BUSINESS CONTEXT I WILL PROVIDE
- Product, category, target market, pricing model, sales motion, and geography
- The priority customer segment and the commercial outcome for this 90-day cycle
- Internal HTML + issues exports exported from Screaming Frog / Sitebulb
- Index evidence sample exported from GSC URL Inspection
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Crawl the site and export status code, canonical, robots directive, title, H1, depth, and indexability.
2. Export indexed and excluded URLs from Google Search Console.
3. Label each URL Keep, Improve, Merge, Redirect, or Remove based on buyer value and uniqueness.
4. Configure: Crawl as desktop, mobile, and rendered JavaScript where the framework requires it.
5. Prioritize: Use severity, revenue exposure, URL count, confidence, and effort instead of crawler defaults.

REQUIRED OUTPUT
Return a table using these exact columns: Crawler | User agent | Rendering | Scope | Max URLs | Data connected | Run owner.
For every recommendation, cite the source row, URL, call note, or data point that supports it.
Add a confidence column in your analysis: High, Medium, or Low.
List missing evidence separately instead of guessing.
Finish with a section named HUMAN DECISIONS REQUIRED.

RULES
- Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts.
- Do not treat correlation as causation.
- Preserve contradictory evidence and explain why it conflicts.
- Do not make the final priority or publishing decision. Prepare the evidence for a human owner.
- Use this example only as a format reference, not as evidence: A parameter URL that duplicates a feature page is “Canonicalize or block”; an old campaign page with backlinks is “Redirect.”

You are assisting a human B2B SaaS SEO and AEO operator with Module 02: Fix crawlability, indexation, and site architecture.

Current lesson: Write an indexation policy
Objective: Templates should have a default rule, so the same problem does not return with every release.
Required artifact: Technical fix queue

BUSINESS CONTEXT I WILL PROVIDE
- Product, category, target market, pricing model, sales motion, and geography
- The priority customer segment and the commercial outcome for this 90-day cycle
- Index evidence sample exported from GSC URL Inspection
- Revenue URL overlays exported from Ahrefs / Semrush
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. List every URL template: product, use case, integration, blog, tag, search, parameter, and utility.
2. Choose index/follow, noindex/follow, canonical target, or disallow only after checking whether crawling is needed.
3. Document the owner and test for each rule before shipping.
4. Reconcile: Compare crawlable, indexable, canonical, sitemap, analytics, backlink, and GSC URL sets.

REQUIRED OUTPUT
Return a table using these exact columns: URL template | Crawl rule | Index rule | Canonical | Sitemap | Minimum value | Owner.
For every recommendation, cite the source row, URL, call note, or data point that supports it.
Add a confidence column in your analysis: High, Medium, or Low.
List missing evidence separately instead of guessing.
Finish with a section named HUMAN DECISIONS REQUIRED.

RULES
- Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts.
- Do not treat correlation as causation.
- Preserve contradictory evidence and explain why it conflicts.
- Do not make the final priority or publishing decision. Prepare the evidence for a human owner.
- Use this example only as a format reference, not as evidence: Integration pages index only when they contain a real workflow, setup detail, and unique value; empty directories remain noindex.

You are assisting a human B2B SaaS SEO and AEO operator with Module 02: Fix crawlability, indexation, and site architecture.

Current lesson: Flatten the revenue architecture
Objective: Important pages should not be orphaned or buried five clicks deep.
Required artifact: Technical fix queue

BUSINESS CONTEXT I WILL PROVIDE
- Product, category, target market, pricing model, sales motion, and geography
- The priority customer segment and the commercial outcome for this 90-day cycle
- Revenue URL overlays exported from Ahrefs / Semrush
- Prioritized audit queue exported from PageOptimized
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Draw the path from homepage to category, use-case, comparison, and integration pages.
2. Add contextual links from high-authority pages using language that explains the destination.
3. Keep priority revenue pages within three meaningful clicks where the site structure allows it.
4. Sample: Inspect representative URLs from every revenue and content template manually.
5. Specify: Write the expected rule, affected templates, acceptance test, and rollback risk for engineering.
6. Ship: Release critical fixes in controlled batches.

REQUIRED OUTPUT
Return a table using these exact columns: Revenue URL | Click depth | Internal links | Orphan | Source hub | Required anchor | Action.
For every recommendation, cite the source row, URL, call note, or data point that supports it.
Add a confidence column in your analysis: High, Medium, or Low.
List missing evidence separately instead of guessing.
Finish with a section named HUMAN DECISIONS REQUIRED.

RULES
- Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts.
- Do not treat correlation as causation.
- Preserve contradictory evidence and explain why it conflicts.
- Do not make the final priority or publishing decision. Prepare the evidence for a human owner.
- Use this example only as a format reference, not as evidence: A reporting guide links to “automated client reporting software,” then the product page links to relevant integrations and comparisons.

You are assisting a human B2B SaaS SEO and AEO operator with Module 02: Fix crawlability, indexation, and site architecture.

Current lesson: Prioritize fixes by impact
Objective: Do not let minor metadata warnings outrank blocked pages or broken templates.
Required artifact: Technical fix queue

BUSINESS CONTEXT I WILL PROVIDE
- Product, category, target market, pricing model, sales motion, and geography
- The priority customer segment and the commercial outcome for this 90-day cycle
- Prioritized audit queue exported from PageOptimized
- Internal HTML + issues exports exported from Screaming Frog / Sitebulb
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Set severity: Critical blocks discovery/indexing; High affects a template or revenue group; Medium reduces clarity; Low is polish.
2. Add affected URL count, traffic/pipeline value, effort, owner, and verification test.
3. Ship critical template fixes first, then validate in a second crawl and URL Inspection.
4. Group: Consolidate issue rows into template-level root causes.
5. Prove: Recrawl, inspect live HTML, and monitor indexation and traffic until the expected state is stable.

REQUIRED OUTPUT
Return a table using these exact columns: Template | Root cause | Affected URLs | Severity | Revenue risk | Owner | Acceptance test.
For every recommendation, cite the source row, URL, call note, or data point that supports it.
Add a confidence column in your analysis: High, Medium, or Low.
List missing evidence separately instead of guessing.
Finish with a section named HUMAN DECISIONS REQUIRED.

RULES
- Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts.
- Do not treat correlation as causation.
- Preserve contradictory evidence and explain why it conflicts.
- Do not make the final priority or publishing decision. Prepare the evidence for a human owner.
- Use this example only as a format reference, not as evidence: Canonicalizing 600 valid integration pages to the homepage is Critical; a title that is three characters long is Low.