sunbeltpulse.com
1 page · 0.5s · Scanned just now
Mostly human-written
72% confidence
The score is a fingerprint of automation, not a quality judgment. A high score means the page reads as machine-generated — not that it is bad.
- Page title
- SunBeltPulse — Sun Belt Real Estate Data & Analysis
- Meta description
- Data-driven real estate intelligence for Sun Belt migration markets. Home price trends, inventory stats, and editorially reviewed market analysis grounded in FRED data for Phoenix, Charlotte, Tampa, Austin, Nashville, Dallas-Fort Worth, Houston, San Antonio, Atlanta, Raleigh, Jacksonville, and Orlando.
- Final URL
- https://sunbeltpulse.com/
- Language
- en
- Built with
- Next.js
SunBeltPulse shows mixed signals leaning toward human authorship. The page pairs a data-product structure (live tracker, comparison tool, real FRED/Census/IRS sourcing) with some marketing-speak framing ("For the mover who wants the numbers"). Copy is thin but grounded—article headlines are specific (e.g., "Jacksonville's Inventory Whipsaw: From 6.1 Months to 3.9 Months in 90 Days"), with real dates and real data sources cited. The layout is custom and product-focused, not templated. Imagery is sparse and functional. The voice wavers between marketing personas and editorial substance, but the substance wins.
- Clear signalContent
Dual-persona framing ('the Pragmatist, the Dreamer') reads like constructed marketing copy, but real article specificity dominates the page
Evidence- “For the mover who wants the numbers — and the partner who wants to know what it feels like to live there.”H1
- “FRED-grounded market data for the Pragmatist, neighbourhood and lifestyle coverage for the Dreamer”body
- “Jacksonville's Inventory Whipsaw: From 6.1 Months to 3.9 Months in 90 Days”H3
Try thisKeep the editorial voice and specific data citations; strip or soften the persona framing ('Pragmatist/Dreamer') to reduce marketing veneer.
- Worth notingTone
Product voice is data-first and editorial, not marketing-first—suggests human product thinking rather than LLM phrasing
Evidence- “Primary data sources: FRED (Federal Reserve)·U.S. Census Bureau·Bureau of Labor Statistics·IRS SOI Migration”body
- “Jacksonville shed nearly two months of supply in a single quarter. Here's what the NEFAR, Houzeo, and FRED data actually show — and why the numbers diverge.”body
Try thisExpand editorial voice across all sections; lean into your data-first authority as a differentiator from generic real estate sites.
Observations of human authorship the page is doing well.
- Structure
Custom product layout built around live data tables and comparison tools, not a boilerplate page-builder template
- Content
Article headlines are specific with real data points, dates, and source citations (NEFAR, Houzeo, TEA ratings, FRED)
- Content35
Mix of boilerplate marketing copy ("the mover who wants", "the Pragmatist, the Dreamer") alongside specific data citations (FRED, TEA ratings, NEFAR) and real article headlines with dates
- Structure25
Intentionally custom layout: data grid with live metro stats, side-by-side comparison tool, mixed article/analysis sections — not a templated hero-features-testimonials sequence
- Imagery20
Only 3 images total with all alt text present; minimal imagery reliance suggests human-built product focused on data tables and text rather than stock photo padding
- Tone35
Personas ("the Pragmatist, the Dreamer") read as constructed marketing framework, but article headlines and data-centric voice throughout suggest real editorial intent and specificity
- Words497
- Images3
- Alt coverage100%
- Internal links62
- External links0
- Schema blocks1
- HTML size113 KB
- Meta tagsMissing canonicalWhy this matters
Why it matters. Title and description are the two strings Google shows in search results — they decide whether anyone clicks. A canonical tag tells Google which URL is the source of truth when the same content lives at multiple paths.
Passing looks like. A non-empty title under 60 characters, a meta description under 160, and a self-referencing canonical link.
Fix. Add the missing tags inside the page head. Treat the title as a headline you'd want to read in a SERP, not a brand slogan.
- Heading structure1 H1, 3 H2Why this matters
Why it matters. Headings are how crawlers and assistive tech understand a page's outline. One H1 names the page; H2s break it into sections. Skipped levels and missing H1s confuse both.
Passing looks like. Exactly one H1, at least one H2, and no skipped levels (no H1 → H3 jumps).
Fix. Replace the missing or duplicate H1 with a single, descriptive heading. Promote section titles to H2; demote sub-points to H3.
- Mobile readinessResponsiveWhy this matters
Why it matters. Google indexes mobile-first. A page without a responsive viewport renders zoomed-out on phones, fails Core Web Vitals on touch, and loses its mobile ranking.
Passing looks like. A meta viewport tag with width=device-width and a layout that reflows under 600px.
Fix. Add a viewport meta tag set to width=device-width and initial-scale=1, then audit your largest blocks at mobile widths.
- Page speed signals0.5s · 113 KBWhy this matters
Why it matters. Page weight and response time directly feed Core Web Vitals. Slow LCP and oversized HTML hurt rankings more than people expect.
Passing looks like. First-byte under 1.5s, HTML payload under 500 KB, fewer than 30 images on the initial render.
Fix. Trim render-blocking scripts, defer non-critical CSS, and serve compressed images sized to the viewport. Move heavy components below the fold.
- Schema markup1 schema blocksWhy this matters
Why it matters. JSON-LD structured data is how you earn rich results — review stars, FAQ accordions, breadcrumbs, article cards. Without it you're competing with one hand tied.
Passing looks like. At least one valid JSON-LD block matching schema.org types relevant to the page (Article, Product, FAQPage, Organization).
Fix. Add an application/ld+json script block describing the page. Validate with Google's Rich Results Test before deploying.
- Broken links4/5 broken in sampleWhy this matters
Why it matters. Broken internal links waste crawl budget, degrade UX, and signal to Google that the site isn't well-maintained. They also cap how deep crawlers reach.
Passing looks like. Every internal link in the sample returns 2xx or 3xx. No dead anchors, no stale paths.
Fix. Use the link list above to spot the broken paths. Either restore the missing pages or update the links to point at live URLs.
- Image alt textAll have altWhy this matters
Why it matters. Alt text is how screen readers describe images and how Google understands what's in them. Missing alts hurt accessibility, image search, and on-page relevance.
Passing looks like. Every meaningful image has a descriptive alt attribute. Decorative images can use alt="" to be skipped intentionally.
Fix. Audit images in /assets and CMS uploads — write alts that describe what's in the image, not what it links to.
Every H1, H2, and H3 we found on the page, in document order.
Show heading outline
- H1For the mover who wants the numbers — and the partner who wants to know what it feels like to live there.
- H2Sun Belt Market Tracker
- H2Two metros. One decision.
- H2Latest Analysis
- H3Jacksonville's Inventory Whipsaw: From 6.1 Months to 3.9 Months in 90 Days
- H3San Antonio Schools Rated: Where to Live If Education Is Your Top Priority
- H3Houston's Flood Insurance Reckoning: Hundreds of Thousands of Homes in FEMA Zones and an Above-Average 2025 Hurricane Season
- H3What would your monthly payment look like?
- H3Sun Belt Weekly Digest
We HEAD-check up to five internal links to spot broken paths quickly.
Show sampled links
- 200 · OKhttps://sunbeltpulse.com/metros/tampa
- No responsehttps://sunbeltpulse.com/metros/orlando
- No responsehttps://sunbeltpulse.com/metros/san-antonio
- No responsehttps://sunbeltpulse.com/metros/phoenix
- No responsehttps://sunbeltpulse.com/metros/houston
Share this scan
Every CrawlRanker scan gets a public, shareable URL. Send it to a client, post it in a thread, or benchmark a competitor.
Preview scan. SEO checks are live; AI scoring is in beta.