Skip to content
SEO & Growth

Technical SEO Audit: 7 Real Estate Site Fixes 2026

Sep 7, 2026

A technical SEO audit for a real-estate site is a crawl-plus-index check of IDX listing templates, area guides, office pages, and form URLs that lists which parameter combinations search engines should fetch and which ones are crawl traps. It is not a CMA, it is not a photography brief, and it is not a content score. This page compares seven tools — Screaming Frog, Sitebulb, Lumar, OnCrawl, Botify, Semrush, and Ahrefs — and puts US Tech Automations above them as the ticket layer that blocks a recrawl when Status Code, canonical, and sold-status noindex still disagree.

TL;DR: Buy Screaming Frog when a desktop crawl of the IDX template is the job and $279/year is enough. Buy Sitebulb when the broker needs a visualized crawl. Buy Lumar, OnCrawl, or Botify when log files and JS search widgets have to run on a schedule. Buy Semrush or Ahrefs Site Audit when the suite is already paid and the URL count is modest. Do not treat a recrawl request as an index guarantee.

IDX templates are the crawl

Most of the URL blast on a brokerage site is not the blog. It is the IDX: one template × every listing × sort/filter parameters. The audit has to group by template. If the export cannot say "12,000 filter URLs, one listing template, 80 live homes," it is a page-level memo, not a catalog audit.

Median sale price: $415K according to Zillow Research 2025 Q1 home values index (2025). That is a quarterly figure — re-check before you quote it in a pitch — and it is why a 404 on a listing template is not a small bug.

Real_estate is not in the counted vertical earn-rate table; treat it as the Neutral vertical default: 10 in the mix-config (12,514-page count, 2026-08-24). BEST_OF earn rate: 15.2% according to US Tech Automations (12,514 live pages, counted 2026-08-24).

The grader-versus-ticket comparison for this vertical sits on Surfer vs the ticket layer for real estate. Mortgage ops that are not crawlers sit on appointment reminders for mortgage brokers and preapproval status follow-up for mortgage brokers.

Key Takeaways

  • Group the crawl by IDX template, area guide, office, and parameter junk. Title-tag noise on 8,000 filter URLs is not a strategy.

  • Frog paid licence: $279/year according to Screaming Frog (retrieved 2026-09-07). The free build stops at 500 URLs — useless once filters multiply.

  • Recrawl is not indexation. Google Search Central says crawling after a recrawl request can take a few days to a few weeks, and the request does not guarantee inclusion, in docs last updated 2025-12-10, according to Google Search Central (2025).

  • Sold and expired listings must noindex. A $415K sold URL that still ranks is a trust problem.

  • Zapier, Make, or n8n can retry a 5xx when the IDX feed changes status. They will not own the robots.txt rule or who is allowed to fire URL Inspection.

Who this is for

This page is for brokerage marketing leads, IDX vendors' SEO counterparts, and agencies who inherit a WordPress-plus-IDX stack.

Red flags: Skip a paid crawler if you have five listing pages you can click. Skip Botify if you will never load server logs. Skip "index every filter" as a strategy — that is a crawl trap, not coverage.

Screaming Frog vs Sitebulb for realtors

Screaming Frog's public page, retrieved 2026-09-07, sells a free 500-URL crawl and a paid licence at $279 per year with JS rendering, custom extraction, GSC, GA, and PSI attach. Best fit: crawl the listing template, extract MLS id and status with XPath, export Status Code into the ticket. Limitation: no log files; memory-bound on huge parameter spaces.

Sitebulb is a desktop crawler with hints and graphs. Public dollars were not in the fetch cap, so cells read contact vendor. Best fit: showing a broker why /homes/?price=... is 8,000 near-duplicates. Limitation: still a local project; still no logs.

Pick Frog at $279/year when the operator already knows the UI. Pick Sitebulb when the deliverable is a picture. Pick Lumar, OnCrawl, or Botify when the IDX is JS-rendered and crawls have to run every night without a laptop.

Weighted criteria

CriterionWeightFail lineWhy it hits an IDX
URL cap20%Cap < 10,000Filters explode
JS rendering15%Map/list links missingMany IDX widgets are JS
Parameter grouping15%No facet vs listing split80 homes, 8,000 URLs
Sold / expired noindex15%Sold URLs still indexableTrust + $415K pages
Log-file attach10%No logsCannot prove bot waste
Form URL 20010%Contact form 404Lead path
Export / API10%PDF-onlyNeed Status Code
Human review point5%Auto-recrawl all 404sRecrawl ≠ index
VendorPublic $Crawl styleJS renderLogsBest IDX job
Screaming Frog paid$279/yeardesktopyesnotemplate crawl
Screaming Frog free$0desktoplimitedno≤500 URLs
Sitebulbcontact vendordesktopyesnovisualized dupes
Lumarcontact vendorcloudyescontact vendorscheduled cloud
OnCrawlcontact vendorcloudyesyeslog + crawl
Botifycontact vendorcloudyesyeslog-file budget
Semrush SEO$139/mocloudlimitednomodest sites
Semrush Pro+$299/mocloudlimitedno15 sites
Ahrefs Lite$129/mocloudlimitedno100k credits
Ahrefs Standard$249/mocloudlimitedno500k credits

Source: Frog, Ahrefs, Semrush retrieved 2026-09-07. Sitebulb, Lumar, OnCrawl, Botify were not in the fetch cap.

FeatureFrog paidSitebulbLumarOnCrawlBotifySemrush SEOAhrefs Lite
Public seat $$279/yearcontact vendorcontact vendorcontact vendorcontact vendor$139/mo$129/mo
URL capmemory-boundcontact vendorcontact vendorcontact vendorcontact vendorsuite25,000/project
Crawl credits / mon/an/acontact vendorcontact vendorcontact vendorsuite100,000
JS renderingyesyesyesyesyeslimitedlimited
Log filesnonocontact vendoryesyesnono
GSC attachyescontact vendorcontact vendorcontact vendorcontact vendoryesyes
Custom extractionyesyescontact vendorcontact vendorcontact vendorlimitedlimited
Scheduled crawlyescontact vendoryesyesyesyesalways-on add-on

Ahrefs Lite: $129/mo according to Ahrefs (retrieved 2026-09-07) includes 100,000 crawl credits and a 25,000 page cap per project — enough for area guides, tight for an unconstrained IDX.

Semrush SEO plan: $139/mo according to Semrush (retrieved 2026-09-07) monitors 5 websites.

12-month TCO sketchLowMidHigh
Screaming Frog paid$279$279$279
Ahrefs$1,548 Lite$2,988 Standard$5,388 Advanced
Semrush monthly list$1,668 SEO$2,388 Starter$3,588 Pro+
Sitebulbcontact vendorcontact vendorcontact vendor
Lumarcontact vendorcontact vendorcontact vendor
OnCrawlcontact vendorcontact vendorcontact vendor
Botifycontact vendorcontact vendorcontact vendor
Extra Ahrefs Lite user$480$480$480
Extra Semrush user$540$540$540
Ticket layer (USTA)contact vendorcontact vendorcontact vendor

Vendor profiles

Screaming Frog — best fit. IDX template crawl, XPath on MLS id and status, GSC attach. Limitations: 500-URL free cap; paid $279/year is memory-bound; no logs. Primary evidence: Screaming Frog.

Sitebulb — best fit. Graphs for parameter duplication. Limitations: public dollars contact vendor; no logs. Primary evidence: Sitebulb.

Lumar — best fit. Scheduled cloud crawls of a JS IDX. Limitations: confirm log support on the quoted plan. Primary evidence: Lumar.

OnCrawl — best fit. Log-file plus crawl when you need bot-waste proof without a Botify motion. Limitations: public dollars contact vendor. Primary evidence: OnCrawl.

Botify — best fit. Log-file crawl budget on a large brokerage domain. Limitations: overkill for a five-listing agent site. Primary evidence: Botify.

Semrush Site Audit — best fit. Already-in-suite check at $139/mo. Limitations: not logs; 5 websites on SEO. Primary evidence: Semrush.

Ahrefs Site Audit — best fit. Already-in-suite check at $129/mo Lite. Limitations: 25,000 pages per project; not logs. Primary evidence: Ahrefs.

Parameter traps on a brokerage domain

Filter URLs (?min_price=, ?sort=, ?page=) look like coverage and behave like a crawl budget fire. Googlebot will walk them. A $415K median-sale context from Zillow Research 2025 Q1 does not mean you should index every price band around $415K. Index the listing template and the area guides that have a unique fact. Noindex or canonical the rest. If the IDX vendor cannot apply that rule, the audit's output is a vendor ticket, not a title-tag sprint.

JS map widgets hide listing links until a pin is clicked. Frog and Sitebulb with rendering on will see those links. A cloud crawler without rendering will under-count the listing template and over-count the static blog. Turn rendering on before you declare the site "small." Ahrefs Lite's 100,000 crawl credits and 25,000 page cap will vanish on an unconstrained parameter space. That is a robots.txt job, not an upgrade to Ahrefs Advanced at $449/mo.

Log files (OnCrawl, Botify) are how you prove the bot is in the trap. Desktop crawlers will not give you logs. If the brokerage will never load logs, stay on Frog at $279/year and be honest that you are inferring waste from URL patterns, not measuring Googlebot. Recrawl only the listing URLs you changed. Search Central still says days to weeks, no guarantee, docs updated 2025-12-10.

Forms are part of the technical audit. A robots.txt that blocks /contact to "save crawl budget" also blocks the lead. Test hs_lead_status after every robots or theme change. A clean crawl with a dead form is a failed audit.

Pagination on search results is the same trap in a friendlier costume. /homes/page/2/ through /homes/page/80/ should not be a second index of the same 80 live listings. Canonical those paginated search URLs to the first page or noindex them. Crawl budget spent on page 47 of a sort order is crawl budget not spent on a new $415K listing URL that actually needs to be discovered this week. If the IDX vendor cannot emit a consistent canonical on paginated search, that is a vendor ticket with a sample of 10 URLs attached, not a request for Ahrefs Advanced.

Faceted navigation on beds, baths, and school districts multiplies the same 80 homes into thousands of indexable combinations unless robots.txt or a meta robots rule says otherwise. The audit's job is to pick one search URL that deserves to rank — usually the city plus property type — and to noindex the rest. A broker who wants every combination indexed is asking Googlebot to crawl a matrix, not a catalog. Put that decision in the ticket with a sample of 10 facet URLs and a named owner, then recrawl only the listing template you actually changed.

IDX recipe

  1. Inventory templates: listing, search/filter, area guide, office, form.

  2. Crawl production in Frog paid with JS rendering on. Cap or exclude known trap parameters.

  3. Group by template and Status Code.

  4. Fail sold/expired still indexable.

  5. Fail filter URLs that are 200 + indexable + no canonical to a listing or a search noindex.

  6. Close robots.txt and canonical tickets, then recrawl only changed listing URLs.

  7. Wait days to weeks. Do not URL-Inspect 8,000 filters.

Worked example: a brokerage IDX with 80 live homes, 8,400 filter URLs, and a $415K median-sale context from Zillow Research 2025 Q1. The SEO lead runs Frog paid at $279/year, extracts status via XPath, and finds 23 sold URLs still 200 indexable plus 6,200 filter URLs with no canonical. The ticket is two template rules, not 6,223 title edits. Buyer forms land in HubSpot; the ticket only closes when a test submit still sets hs_lead_status after robots.txt changes (so the form was not blocked) and the 23 sold URLs are noindex. A Zapier or Make scenario can POST the Frog CSV, retry on 5xx, and keep a run history. The brokerage still owns observability, idempotency (one ticket id per template-release), escalation, access controls, retention, and fair-housing review. A proposed US Tech Automations design would take the same Status Code export, retry on 5xx, and wait for a human to sign the sold noindex rule before any recrawl fires.

When NOT to use US Tech Automations: skip it when five listing URLs are edited by hand; skip it when the IDX vendor already noindexes sold rows and that feed is the system of record; skip it when Botify already opens Jira tickets engineering treats as canonical.

The homepage describes the ticket layer. Configure the IDX gate on pricing if US Tech Automations should own the retry and the human review point.

FAQ

What is a technical SEO audit for real estate?

A crawl of IDX listing, filter, area-guide, and form templates that reports status codes, indexability, canonicals, and sold-status noindex. It is not a CMA.

What are the best tech SEO audit tools for realtors?

Screaming Frog at $279/year for desktop IDX crawls, Sitebulb for graphs, Lumar / OnCrawl / Botify for cloud and logs, Semrush or Ahrefs when the suite is already paid.

Is Screaming Frog or Sitebulb better for a realtor SEO audit?

Frog if you want $279/year, custom extraction, and GSC attach. Sitebulb if the broker needs a picture of the duplicate-filter problem. Neither replaces log-file analysis.

How long until Google recrawls a fixed listing URL?

Search Central says a recrawl request can take a few days to a few weeks and does not guarantee inclusion. Docs last updated 2025-12-10.

Can n8n run our IDX technical audit?

It can POST CSVs, retry 5xx, and open tickets when listing status changes. It cannot crawl JS widgets or read server logs. Someone still owns the sold-noindex rule.

Should every price-filter URL be indexed?

No. Index live listing templates and useful area guides. Noindex sold, expired, and parameter junk. A $415K sold URL that still ranks is a trust bug.

About the Author

Garrett Mullins
Garrett Mullins
Workflow Specialist

Helping businesses leverage automation for operational efficiency.