7 Technical SEO Checks for Property Portfolios 2026

Technical SEO for property management is a crawl of community, floor-plan, amenity, and office URLs so Google can fetch the live unit catalog, not a renovation 404 or a faceted "available now" duplicate. It is not on-page copywriting, it is not an ILS feed, and it is not a recrawl that guarantees occupancy. Screaming Frog, Sitebulb, Oncrawl, Lumar, Botify, JetOctopus, and ContentKing are the seven spiders and monitors in this shortlist. US Tech Automations sits above them as the ticket layer that blocks a community URL when the crawl status, the unique fact, and the NAP string have not all passed.

TL;DR: Buy Screaming Frog for desktop list-mode crawls of a CMS export. Buy Sitebulb for hint templates. Buy Oncrawl, Lumar, Botify, or JetOctopus when logs and schedules matter. Buy ContentKing when midnight template edits are the risk. Do not crawl the resident portal as if it were the marketing site.

Catalog crawl for unit URLs

A property marketing site is a catalog. Google's ecommerce guides tell stores to share product data, add relevant structured data, and design crawlable URL and site structure so Google can parse catalog pages, according to Google Search Central. Floor plans are the SKUs. Community pages are the category nodes. "Available now" facets are the filters that waste budget if they enter the sitemap.

Institutional fee: 3-5% of GPR according to IREM (2024 Management Compensation Survey). Range, not a point. Smaller portfolios pay more on that survey's note (8-12% is the sibling caution, not a second IREM citation). The crawl seat has to live inside the fee, not as an unbounded agency line.

BEST_OF earn rate: 15.2% according to US Tech Automations (2026) on 12,514 live pages counted 2026-08-24.

'7 Best' earn rate: 25.5% according to first-party Phase 1 count (2026) versus 14.0% for '5 Best' on the same count.

Screaming Frog free cap: 500 URLs according to Screaming Frog. Four communities with floor-plan children usually blow the cap on pass one.

ContentKing job: real-time watch according to ContentKing positioning — use it when template edits are the incident, not when you still need a 1,200-URL bulk spider.

Who this is for

This page is for marketing leads at fee managers and owner-operators who already have a property CMS, Search Console, and a sitemap that may include too many facets. The pain is renovation 404s, duplicate titles across cities, and a resident portal mixed into the marketing crawl.

Red flags: Skip a cloud crawler if you can still open every community URL by hand. Skip Screaming Frog if nobody will run a desktop licence. Skip ContentKing if you wanted a one-off audit. Skip the category if you expect the spider to write listing copy.

Key Takeaways

• Technical SEO for property management is fetchability of community and unit URLs, not a content score.

• Screaming Frog wins desktop list mode; Sitebulb wins hints; Oncrawl, Lumar, Botify, and JetOctopus win logs; ContentKing wins monitoring.

• 3-5% of GPR is the IREM 2024 institutional fee range already cited — the crawl has to fit that fee.

• IA, cost, and CMS choice are separate: multilocation SEO for property management, property management SEO cost, small-landlord software.

• A ticket layer is optional when a coordinator already fails 404 floor plans in a weekly sheet.

Glossary for property crawls

• Community URL: marketing page for one property.

• Floor-plan URL: the "SKU" in the catalog metaphor.

• Facet URL: available-now or sort parameters that should usually stay out of the sitemap.

• Resident portal: authenticated rent-pay host; crawl separately or not at all.

• GPR: gross potential rent; 3-5% institutional fee in the IREM 2024 survey already cited.

• coverageState: Search Console URL Inspection field in the worked example.

• List mode: Screaming Frog crawl of a CSV, not a follow-links spider from the homepage.

• Ticket: one URL, one owner, one fail reason.

Weighted criteria for portfolio crawls

Source: editorial weights. IREM 3-5% and Screaming Frog's 500-URL cap are attributed in the body.

Platform shortlist

Flags are public product-family positioning. Only the 500-URL free cap is a public number on this page.

Screaming Frog. Best fit: an SEO lead who will paste a CMS export of community and plan URLs into list mode and turn on JS rendering for apply CTAs. Limitations: 500-URL free cap; not a scheduler. Implementation: list mode, custom extraction for canonical and h1, export 404s. Primary evidence: Screaming Frog.

Sitebulb. Best fit: hint templates for the next community launch. Limitations: contact vendor. Implementation: crawl, fail duplicate titles, export hints. Primary evidence: Sitebulb.

Oncrawl. Best fit: log-based proof that Googlebot is wasting hits on facets. Limitations: contact vendor. Implementation: connect logs, cut parameter URLs from the sitemap. Primary evidence: Oncrawl.

Lumar. Best fit: scheduled cloud crawls plus logs. Limitations: enterprise motion. Implementation: weekly crawl of community and plan templates. Primary evidence: Lumar.

Botify. Best fit: large graphs with JS and logs together. Limitations: not a small-landlord seat. Implementation: compare HTML crawl with log lines. Primary evidence: Botify.

JetOctopus. Best fit: cloud crawl bakeoff alternative. Limitations: contact vendor. Implementation: same CMS export as Frog. Primary evidence: JetOctopus.

ContentKing. Best fit: real-time watch when a vendor edits the title tag on 40 communities at once. Limitations: monitoring, not a substitute for the first 1,200-URL bulk crawl. Implementation: watch community templates, alert on noindex or 404. Primary evidence: ContentKing.

If the CMS cannot emit unique facts, fix the software first using the small-landlord shortlist already linked. If the IA is the hole, use the multilocation post already linked. If you do not know the program cost, use the cost post already linked.

TCO notes

Source: Screaming Frog for the 500-URL cap. Other list prices contact vendor. TCO must fit inside the 3-5% GPR fee already cited, plus the human who confirms renovations.

Worked example: 1,200 marketing URLs

A fee manager with 4 communities, 1,200 HTML marketing URLs, and a 14-day SLA exports the CMS list on Monday. Screaming Frog list mode returns 1,048 200s, 96 301s, and 56 404 floor plans after a renovation. Those 56 become tickets. Search Console URL Inspection on a sample of 12 repaired plans shows coverageState still excluded on 5 of 12, so recrawl is filed only on the 5, not the 1,200. When Stripe later posts invoice.paid on the marketing retainer, that is 1 payment, not 56 fixes. Zapier, Make, or n8n can POST the crawl CSV, retry on 5xx, and keep a run history. The operator still owns idempotency (one ticket per URL), who may request indexing, retention of the CSV, and the manager who signs the 56 failures. A proposed US Tech Automations design would refuse to mark the community live until coverageState plus a unique-fact checkbox pass — it would not skip the spider, and it would not promise indexation inside the 14-day SLA, and it would not treat 3-5% GPR as a ranking factor.

Facets, sitemaps, and the portal split

"Available now" and sort parameters should not enter the marketing sitemap. If the CMS emits them, noindex them or robots-disallow the parameter space after you confirm Googlebot is wasting hits — that confirmation is why Oncrawl, Lumar, Botify, or JetOctopus exist. A desktop Frog crawl of a CMS export will not show log waste. Do both if the portfolio is large enough that 3-5% of GPR (IREM 2024, already cited) is paying for a cloud seat.

The resident portal is a different host. Authenticated rent-pay URLs, work-order URLs, and resident news should not share a Search Console property with community marketing URLs. Mixing them inflates excluded-by-noindex charts and hides renovation 404s. If a vendor insists on one property, you will spend the audit explaining false alarms instead of fixing 56 floor plans.

Sitemaps should list the live community and plan URLs only. When a plan 404s, remove it from the sitemap the same day you file the ticket. Recrawl the repaired URL, not the domain. ContentKing can watch the template; it cannot invent the sitemap discipline.

Mistakes on property graphs

• Crawling the resident portal and the marketing host as one property.

• Leaving available-now facets in the sitemap.

• Requesting recrawl on the whole domain while 56 plans still 404.

• Buying Botify for a 40-URL brochure site.

• Treating ContentKing alerts as a unique-fact audit.

• Stitching zaps that retry forever without an idempotent URL key.

What 3-5% of GPR does not buy

The IREM 2024 institutional fee range already cited (3-5% of GPR; smaller portfolios pay more) is the budget envelope for the marketing site, the ILS, and the crawl seat together. It does not buy Botify by default, and it does not buy a recrawl that Google is not obligated to honor. If the fee cannot cover a human who fails 56 renovation 404s, a cloud crawler will only produce a prettier CSV. Screaming Frog's 500-URL free cap already cited is the small-portfolio tripwire: pay the licence or stop crawling floor-plan children on the free spider.

Multilocation IA, SEO cost, and CMS choice remain the three posts already linked. Technical SEO is the fetch layer under all three. A 200 on a clone community is still a clone. A sitemap row that 404s is a ticket the same day, not a monthly report. Keep renovation 404s on the same punch list as unit turns so leasing and marketing share one URL owner. If nobody owns the 56 failed plans, the cloud crawl is just a more expensive CSV. Put the URL owner on the same unit-turn sheet the leasing team already uses so marketing is not the only desk that sees a 404 after a renovation. If leasing will not share turn dates, the 56 failed plans in the worked example will keep reappearing on every monthly crawl as if they were new. Name the leasing contact on the crawl runbook so the 404 owner is a person, not a queue.

Stitching it in Zapier

The real alternative is Screaming Frog plus a sheet plus a Make scenario that opens a ticket when status ≠ 200. Those tools can support run histories, retries, error branches, and audit evidence when configured. You must still design observability, idempotency, escalation, access controls, retention, and maintenance. If a weekly meeting already fails renovation 404s, you do not need a second platform on day one.

When a ticket layer is the wrong seat

Do not buy US Tech Automations if a coordinator already fails 404 floor plans in a weekly sheet and Screaming Frog is the only crawl you will ever need. Do not buy it if you have two community URLs and URL Inspection is enough. Do not buy it if the hole is ILS feeds or paid media — a spider will not fill units.

Questions operators ask

What is technical SEO for property management?

Technical SEO for property management is the crawl of community, floor-plan, and amenity URLs that records status codes, canonicals, render, and indexability so you can fix fetch errors before you request a recrawl. It is not on-page scoring. The seven tools here crawl or monitor that graph.

Is Screaming Frog enough for a portfolio?

Screaming Frog is enough when someone will run list mode, pay past the 500-URL free cap, and export failures. It is not enough when you need schedules, logs, or midnight monitoring. That is the cloud four or ContentKing.

Should we crawl the resident portal?

No. Keep the marketing host and the authenticated portal in separate properties. Rent-pay URLs should not be in the marketing sitemap. Mixing them hides the 56 floor-plan 404s that cost tours.

Can we stitch this in Zapier instead?

Yes. Zapier, Make, or n8n can ingest a crawl CSV, retry 5xx, and keep history. You still own who requests indexing, idempotent URL keys, and retention. That is enough until the gate rules are the product.

How does this relate to multilocation SEO?

Multilocation is IA and unique facts across communities — already linked. Technical SEO is whether those URLs fetch. You need both. A 200 on a clone is still a clone.

Do we need structured data on floor plans?

Google's ecommerce guides already cited say to add relevant structured data so catalogs parse. Mark up visible facts only. Do not invent availability in JSON-LD that the PDP does not show.

Next step

If the spider already shows which floor plans 404 and the gap is a human-signed gate, start on the homepage and open pricing with the URL list and the 14-day SLA. Do not ask the ticket layer to replace Screaming Frog.