sunbeltpulse.com
1 page · 0.2s · 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. It doesn't mean the page 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-US
- Built with
- Next.js
SunBeltPulse shows strong human authorship signals. The content is grounded in specific real-world data (FRED, BLS, Census Bureau) with precise metrics (Phoenix -5.0% YoY, 82 days on market), not generic marketing phrases. The page has a coherent voice addressing a specific audience (relocating couples), and the structure, while organized, doesn't follow a templated AI-builder pattern. Imagery includes proper alt text and appears to be data-driven rather than stock. Low AI signals across all dimensions point to intentional, data-first product design rather than AI generation.
- Worth notingContent
Some sections use broad real-estate phrasing typical of web copy
Evidence- “Deep dives into Sun Belt market data, trends, and opportunity”H2
- “migration signals, and lifestyle notes”body
Try thisPush headlines toward specificity: replace 'Deep dives into trends' with article titles or specific findings (e.g., 'DFW Payrolls Up 41.9K, Wages Up Only 1.8%').
- Worth notingImagery
All images have alt text, suggesting human review; content itself unclear from truncated crawl
Evidence- “6 images, missing alt: 0”page
Try thisEnsure images remain custom data visualizations or product screenshots; avoid stock photo expansion as the site grows.
Signals of human authorship the page is doing well.
- Content
Grounded in real data sources (FRED, Census, BLS) with specific metrics (Phoenix -5.0% YoY, 82 days on market April 2026) rather than generic claims
- Tone
Distinct voice targeting relocating couples with two personas (Pragmatist for data, Dreamer for lifestyle) — shows editorial intent and audience understanding
- Content22
Specific data points (6.36% mortgage rate, Phoenix -5.0% YoY, 49d average days on market) with domain expertise; minimal generic phrasing
- Structure35
Clear hierarchy with market tracker, compare tool, and analysis sections; mostly custom layout rather than templated AI-builder structure
- Imagery25
6 images with all alt attributes present; appear to be data visualizations or custom graphics rather than stock photos or AI-generated visuals
- Tone35
Clear voice targeting couples ("for the mover who wants the numbers — and the partner who needs the feel") with distinct personas (Pragmatist, Dreamer)
- Words662
- Images6
- Alt coverage100%
- Internal links80
- External links0
- Schema blocks1
- HTML size150 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 to 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.2s · 150 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. Skip it and Google has nothing structured to pull from when it builds your SERP card.
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 what screen readers read aloud, and what Google reads instead of pixels. Skip it and you lose on both fronts.
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 needs the feel.
- H2Sun Belt Market Tracker
- H2Two metros. One decision.
- H2Latest Analysis
- H3DFW Job Market 2026: Payroll Rebound, Wage Slowdown, and What It Means for Relocators
- H3Phoenix Days on Market Surges 55% Year-Over-Year: April 2026 Analysis
- H3Austin's Pandemic Boomerang: What Redfin's Net Outbound Migration Data Means for the Housing Market
- H3Phoenix Home Prices Down 5.2% YoY: What the Deepest Drop of the Cycle Means for Buyers and Investors
- H3Phoenix Days on Market Surge: What 51–100 Days Tells Buyers and Investors About the 2026 Market
- H3Jacksonville's Inventory Whipsaw: From 6.1 Months to 3.9 Months in 90 Days
- H3What would your monthly payment look like?
- H3Planning the whole move?
- H3Sun Belt Weekly Digest
We HEAD-check up to five internal links to spot broken paths quickly.
Show sampled links
- No responsehttps://sunbeltpulse.com/metros/tampa
- No responsehttps://sunbeltpulse.com/contact
- No responsehttps://sunbeltpulse.com/compare/charlotte-vs-nashville
- 200 · OKhttps://sunbeltpulse.com/metros
- No responsehttps://sunbeltpulse.com/compare/dallas-vs-houston
Was this report useful?
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.