## **🌡️ What These Audit Flags Mean**

Climate-audit and active sitemap reviews can identify pages with repeated FAQ content or missing content sections. These flags describe structural patterns, not automatic proof that every page needs the same fix. A page may be flagged because its template is incomplete, content did not load during the scan, or similar sections were published more than once.

## **📊 Validate the Scope First**

Before editing pages, confirm the findings against the live site and the current sitemap:

1. Open **OTTO SEO → All Audits** or **OTTO SEO → Crawl Monitoring** to review the audit results.
2. Compare the staging findings with live production pages.
3. Confirm whether the reported count matches pages currently listed in the active XML sitemap.
4. Separate results into high-confidence duplicate FAQ pages, medium-confidence structure issues, and clean pages.
5. Manually review a representative sample so decisions are not based only on automated detection.

Counts can differ between audit screens when scans, sitemap data, or domain analysis are still updating. Refresh the audit after the crawl and sitemap data are available. Previously reported sitemap scheme and duplicate-row issues may also affect older results.

## **🧩 Define the Correct Page Structure**

Choose five to ten representative pages across templates, locations, and issue types. Compare them with approved reference pages, such as Glendale AZ, Tucson AZ, or Boston. Document the intended structure before making bulk changes.

For each template, decide how to handle:

- Duplicate FAQ content: retain one accurate FAQ section and remove or rewrite repeated copies.
- Intro copy: keep a clear, unique introduction that matches the page location and intent.
- “Common Plumbing Challenges”: retain it only when it adds useful, page-specific information.
- Missing **content3Summary**, **wcrrContent**, or **content7Summary**: determine whether the field is required for that template or should remain intentionally empty.
- Pages needing substantial changes: mark them for rewrite or rebuild instead of applying a mechanical fix.

## **🧪 Run a Staging Pilot**

Repair a small batch of approximately 10–25 pages in staging. Include different templates and severity levels. After the changes:

1. Refresh the site or audit cache.
2. Review the rendered pages, not only the stored content fields.
3. Check headings, intro copy, FAQ placement, section order, links, and page-specific details.
4. Compare before-and-after results and record any pages that still need manual rewriting.
5. Keep an export or rollback copy of every changed row.

## **🚀 Roll Out Repairs in Waves**

After the pilot passes QA, remediate pages in controlled waves. Prioritize active sitemap pages, then address high-severity findings before medium-severity structure issues. Run every wave through staging and QA before promoting it to production. Continue monitoring the sitemap and rerun the audit after each release.

## **📌 Set Practical Expectations**

A small climate-audit set, such as 70 pages, may be fixable within a week when the scope is limited and the repair recipe is clear. A set of 2,475 high-severity active sitemap pages is not suitable for manual cleanup in one week. A broader set of 3,760 pages with any structural flag requires automated or semi-automated remediation, staged testing, and multiple review waves.

## **🛠️ Where to Review and Create Content**

Use **OTTO SEO → All Audits** for audit findings and **Content → Content Genius** for page rewrites or new content. Content Genius includes options to write, generate, rework, or create content in bulk. Use bulk actions only after the target structure has been approved and the pilot confirms that the output is accurate.

## **💬 Get Help**

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.