> For the complete documentation index, see [llms.txt](https://support.agentfire.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.agentfire.com/spark-editor/website-audit-content-findings.md).

# How to Handle Content Findings in a Website Audit

What website audit findings about hidden headings, stat counters and leftover placeholder content mean on an AgentFire website, and which ones need a fix.

Site audit tools like Screaming Frog and Semrush often flag the same few content findings on AgentFire websites. Some are false positives you can ignore, and some are worth fixing.

## Which findings need action

| Finding                                                                                  | What it is                                                | What to do                                                                         |
| ---------------------------------------------------------------------------------------- | --------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| Hidden or duplicate headings, like an "Insert/edit link" H1 or an unrendered template H2 | Hidden system markup, not your page content               | Nothing                                                                            |
| Animated stat counters (like a sales total) that show 0                                  | The counter's starting number, shown before it animates   | Use static text, or set the starting number to the final number                    |
| Area guide or Market Snapshot stats that show 0 in the HTML                              | A separate issue that has been fixed                      | See the area guide and Market Snapshot stats question under Common Questions below |
| Duplicate head or body tags                                                              | Layout wrappers that don't affect indexing                | Nothing                                                                            |
| Paginated blog pages that canonicalize to `/blog/`                                       | Intended behavior                                         | Nothing                                                                            |
| The support email in the AI search widget's script                                       | Fixed. The public message is now neutral                  | Check again, since an old cached page may still show it                            |
| Placeholder contact details, demo cities or demo landing pages                           | Template defaults that should have been replaced at setup | Email support to remove them                                                       |

## What Support covers

Support fixes specific issues. To get something fixed, send <support@agentfire.com>:

* The page URL
* The element on the page
* What you expected to see
* The correction or replacement content

A screenshot helps.

A full audit of every form, IDX search, navigation path, photo or professional claim, without a specific issue to fix, is outside standard Support. If something isn't working, like a form that doesn't send or pages Google can't reach, that's a specific issue: send us the page addresses and what you saw, and we'll check it.

Marketing strategy and brokerage-approved claims stay with you. Office Hours is the place to learn the tools hands-on, and for deeper SEO and AEO work, we can introduce you to [FlyDragon](https://goflydragon.com), AgentFire's trusted AEO and SEO partner. FlyDragon is a separate company with its own paid service.

## Where to edit SEO titles, meta descriptions, headings, slugs and alt text

Use this table to find where to change each page's SEO title and description, headings, image descriptions (alt text) and page address (slug):

| What                             | Where to edit it                                                                                                                                                                                                                                                                                                                                                                                            |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SEO titles and meta descriptions | In the page editor, click the **Y** icon to open the page settings. Scroll to **Yoast SEO** and click **Edit snippet**. On a blog post, **Edit snippet** is under **Yoast SEO** in the post editor. It has a built-in character counter.                                                                                                                                                                    |
| Headings                         | The post title is the H1. Body headings are set in each block.                                                                                                                                                                                                                                                                                                                                              |
| Page address (slug)              | Edit the **Slug** field in the same **Edit snippet** panel. If you change the address of a live page, [add a 301 redirect](https://support.agentfire.com/google-search-console/google-search-console/google-search-console-page-indexing-errors.md#redirect-a-page-that-moved) from the old address in **AgentFire Settings** > **Redirect Manager**, or email <support@agentfire.com> and we'll set it up. |
| Image alt text                   | The alt text field in the **Media Library**. Until you fill it in, an image's alt text defaults to its file name.                                                                                                                                                                                                                                                                                           |
| Internal links                   | Press Ctrl+K (Cmd+K on a Mac) in the editor.                                                                                                                                                                                                                                                                                                                                                                |
| XML sitemap and robots.txt       | Managed automatically.                                                                                                                                                                                                                                                                                                                                                                                      |

## Common Questions

<details>

<summary>An audit or SEO report flags duplicate or hidden headings, like an "Insert/edit link" H1 or an unrendered template H2. Is this a problem, and should they be removed?</summary>

No. These headings come from hidden system templates, like the link editor and account pop-ups, not your page content. They're there by design.

Visitors never see them, and search engines don't treat them as competing headings. Audit tools flag them because they can't tell visible content from system markup, so this is a false positive.

</details>

<details>

<summary>Animated stat counters show 0 to crawlers and website checkers instead of the real total. Is that an SEO problem?</summary>

Yes, it can be. The Counter widget, like one showing an animated sales total, prints its starting number (0 by default) as visible text. The final number only exists in a `data-to` attribute, and JavaScript animates to it after the page loads or when the counter scrolls into view. Crawlers that read the raw HTML in the page source see 0 (zero) instead of the total. The legacy Counter widget works the same way.

To avoid it, use static text, or set the counter's starting number equal to its final number. You can also email <support@agentfire.com> and we'll replace a counter with static text for you.

This is separate from area guide and Market Snapshot stats, which had their own issue with 0 in the HTML. That issue has been fixed.

</details>

<details>

<summary>Do area guide, neighborhood Highlights and Market Snapshot stats still show 0 (zero) in the page source (HTML) until they load in the browser?</summary>

No. Area guide stats, like the neighborhood Highlights widget, and Market Snapshot stats used to show a 0 or $0 placeholder in the page source (HTML) until the stats loaded and animated in the browser, so crawlers that don't run JavaScript or scroll the page saw zero. This has been fixed, and the fix is live.

If your area stats are missing or look wrong for a small area, that's a separate data issue. See [Area Guides Frequently Asked Questions](https://support.agentfire.com/site-tools/area-guides/area-guides-frequently-asked-questions.md).

</details>

<details>

<summary>The audit flags duplicate head or body tags, or paginated blog pages that canonicalize to /blog/. Is that a problem?</summary>

No. The duplicate head and body tags are wrappers from the page layout builder, and they don't affect indexing.

Paginated blog pages canonicalize to `/blog/` by design. Individual pages and posts use Yoast for their canonical URLs.

</details>

<details>

<summary>An audit flags support@agentfire.com in the AI search widget's script. Is that placeholder contact info?</summary>

No, and it has been fixed. The public page source used to include `support@agentfire.com` in the AI search widget's error message. That message is now neutral.

The email only appears in the AI modal shown to signed-in admins, not in the public page source. If you still see it, check again, as you're most likely looking at an old cached copy of the page.

</details>

<details>

<summary>My website shows placeholder contact details, demo cities or demo pages. Can you remove them?</summary>

Yes. A placeholder address, phone number or AgentFire email in your contact details, demo cities, and demo landing pages are template defaults that should have been replaced when your website was set up. Email <support@agentfire.com> and we'll remove them.

Demo landing pages, like `/nosey-neighbor/`, aren't linked from your navigation, but we'll take them down so they can't be found.

</details>

<details>

<summary>Can you scan my whole site for leftover template or demo content?</summary>

A sitewide scan is outside standard Support, but there's an easy way to do it yourself. Claude in Chrome, the Claude browser extension, can go through your site and list potential leftovers, like demo contact details or demo-city pages.

It's an optional tool and may not catch everything, so review the list it creates. Then send the items you want fixed to <support@agentfire.com> and we'll take care of them.

</details>

<details>

<summary>Will AgentFire check every form, search, photo and claim on my website, or audit or verify my whole site, including every page and image?</summary>

No. Support fixes specific issues, so send us the page URL, the element, what you expected, and the correction or replacement. See [What Support covers](#what-support-covers) for details.

Office Hours is the place to learn the tools hands-on, and marketing strategy and brokerage-approved claims stay with you. For deeper SEO and AEO work, we can introduce you to FlyDragon.

</details>

<details>

<summary>I have a long AI or technical audit report. How do you handle it?</summary>

Reports like these often focus heavily on technical items without context about how the platform works, and there's no one-time fix that gets results on its own. The things that matter most are unique content, verified reviews on sites like Google, Zillow and Yelp, and brand mentions. See [How to Get Found on Google and in AI Answers (SEO and AEO)](https://support.agentfire.com/coaching-and-success/tips-tricks/seo-is-dying-heres-what-real-estate-agents-should-do-instead.md) and the **Myth Buster** section of [AgentFire's AEO + SEO Guide](https://aeo-seo-guide.agentfire.com/).

For content changes, send us the specific pages and the new text you want. If the report shows something that isn't working, like pages Google can't reach, server errors or a broken form, send us the page addresses and what the report found, and we'll check it. For hands-on help with the rest, we recommend FlyDragon.

</details>
