SEO report for www.swvtchamber.com
https://www.swvtchamber.com/ · checked Wed, 11 Nov 2026 12:15 GMT
Fix these first
- Render-blocking resourceshigh
0 blocking script(s) and 9 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- H1 headingcritical
4 H1 headings – one clear H1 is best practice.
Fix: Use one H1 that states the page topic with its main keyword.
On Squarespace: Select the main heading text and choose Heading 1 from the text style menu; use Heading 2 for the rest.
- Readabilitymedium
Flesch reading ease 20 (difficult), about 25 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- HTML sizemedium
922 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- Scripts & third partiesmedium
79 script tag(s); files loaded from 10 other domain(s): images.squarespace-cdn.com, use.typekit.net, assets.squarespace.com, definitions.sqspcdn.com, static1.squarespace.com, pagead2.googlesyndication.com….
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- Imagesmedium
32 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- HSTSmedium
HSTS: max-age=0
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to swvtchamber.com…
Indexing & crawling 100%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap found at https://www.swvtchamber.com/sitemap.xml with 870 URLs.
Declared in robots.txt.
This page is NOT listed in it.
Most recent lastmod: 2026-11-05.
- ✓
Canonical URLhigh
Canonical: https://www.swvtchamber.com
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://bennington.com/ → https://www.swvtchamber.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
swvtchamber.com redirects to www.swvtchamber.com.
Search snippet & sharing 88%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“Southwestern Vermont Chamber of Commerce”
About 417px of Google's ~580px desktop width.
- !
Meta descriptionhigh
472 characters, ~2931px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
On Squarespace: Pages panel → gear icon on the page → SEO tab: fill in the SEO description.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en-US"
Content quality 63%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
497 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- ✗
Readabilitymedium
Flesch reading ease 20 (difficult), about 25 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✓
Topic focushigh
4 of 4 title keywords appear in the main content.
- !
H1 headingcritical
4 H1 headings – one clear H1 is best practice.
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
On Squarespace: Select the main heading text and choose Heading 1 from the text style menu; use Heading 2 for the rest.
- ✓
Heading structuremedium
5 headings for 497 words.
Levels are in order.
- ✗
Text-to-code ratiolow
1% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 66%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✗
Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- !
Entity clarityhigh
Identified as: Organization, LocalBusiness.
1 official profile link(s) (sameAs).
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✓
Freshness signalsmedium
The page shows when it was published or last updated.
- !
Trust pages (E-E-A-T)medium
Links found to about and contact; missing privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
3 JSON-LD block(s): WebSite, Organization, LocalBusiness.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Recommended but missing: Organization.name, Organization.url, Organization.logo, LocalBusiness.telephone, LocalBusiness.url.
Links 88%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
132 internal and 61 external links.
- !
Anchor text qualitymedium
Same text used for different pages: “read more →”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 33%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
254 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✗
HTML sizemedium
922 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with gzip.
- ✗
Render-blocking resourceshigh
0 blocking script(s) and 9 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
79 script tag(s); files loaded from 10 other domain(s): images.squarespace-cdn.com, use.typekit.net, assets.squarespace.com, definitions.sqspcdn.com, static1.squarespace.com, pagead2.googlesyndication.com….
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
32 image(s).
28 without width/height – can cause layout shift (CLS).
28 image(s) after the first three aren't lazy-loaded.
4 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✗
Cachinglow
No Cache-Control header.
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 75%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✗
HSTSmedium
HSTS: max-age=0
max-age is under 6 months – browsers will forget it quickly.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✗
Security headerslow
Present: nosniff.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 80%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 32 images have alt text.
- ✓
Link nameslow
Every link has a readable name.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO 25%
Signals that help you appear in Google Maps and 'near me' searches.
- !
LocalBusiness markuphigh
LocalBusiness markup includes: address, openingHoursSpecification.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
On Squarespace: Fill in Settings → Business information. For full markup, paste our schema generator's code into Settings → Advanced → Code Injection → Header (Core plan and above).
- ✗
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
Fix: Show the same business name, area and phone/email as your Google Business Profile.
- ✗
Map & directionslow
No map or directions link.
Fix: Add a Google Maps directions link so customers can find you.