route3shop.com scored 40/100 on the website scan.
Needs work
route3shop.com · Scanned 2026-11-16
47 passed16 warnings13 failed
- Technical SEO & indexability7/10 of 10 points
- On-page SEO & content14/25 of 25 points
- AI search / AEO / GEO readiness4/35 of 35 points
- Local SEO & entity signals0/5 of 5 points
- Speed, scripts & mobile13/20 of 20 points
- Conversion & lead generation2/5 of 5 points
Why AI search is 35 of the 100 points
Google is sending fewer people to websites. When it answers with an AI Overview, the top-ranked page's click rate is 58% lower than it would otherwise be (Ahrefs, 300,000 keywords, December 2023 against December 2025), and 68% of Google searches now end without a click at all (SparkToro, January–April 2026). The answer comes more and more from Google's AI, ChatGPT, Gemini and Perplexity, and they name the businesses whose sites they can read and quote. That is what this part of the scan measures, so it carries the most points. Every area's points fall faster than its checks: a warning counts a quarter of a pass, and an area half done earns about a third of its points, because search and AI answers go to the sites that finish the work.
What to fix first
-
✗
FAQPage schema +6 points
No FAQ — not in the schema and not on the page. Question-and-answer blocks are what the answer engines lift most readily.
What we’d do: Every substantive page carries a visible FAQ with FAQPage schema built from the same text.
-
✗
llms.txt +6 points
No llms.txt at the site root. ChatGPT, Claude and Perplexity have to piece the business together from the pages.
What we’d do: Every site ships an llms.txt written from its facts: who, what, where, the proof, the pages.
-
✗
Questions answered on the page +6 points
No question is asked and answered on the 1 page read. When someone asks ChatGPT or Google's AI about a service, the engines quote pages that ask that question and answer it in a sentence or two.
What we’d do: Every service page answers the questions people ask about that service — four or more, each asked as a heading and answered in its first sentence — with FAQPage schema from the same text.
-
!
Page title +3 points
“Affordable Used & Refurbished Appliances — Route 3 Liquidation” is 62 characters. Google shows about 60 and cuts the rest, so the end of it is lost in results.
What we’d do: We write titles of 30–60 characters, the topic first and the brand last, so nothing is cut.
-
!
Meta description +3 points
163 characters. Google shows about 160 and cuts the rest with an ellipsis.
What we’d do: We write descriptions of 120–160 characters, the point first.
Every check, by category (103 checks)
Technical SEO & indexability 7 of 10 points
-
✗
Sitemap
No sitemap found or at /sitemap.xml, /sitemap_index.xml or /wp-sitemap.xml. Crawlers have to discover every page by following links.
What we’d do: A sitemap generated from the site's pages on every build, named in robots.txt and submitted to Google and Bing on every deploy.
-
!
Canonical URL
No canonical link. With www, trailing-slash and tracking variants of the URL, Google has to guess which one to index.
What we’d do: Every page names itself as its own canonical URL.
-
!
Security headers
Missing: Content-Security-Policy, frame protection (X-Frame-Options or CSP frame-ancestors).
What we’d do: Content-Security-Policy, X-Content-Type-Options, frame protection and Referrer-Policy on every response.
-
!
Sitemap named in robots.txt
robots.txt has no Sitemap: line — Google and Bing have to find the sitemap some other way.
What we’d do: Every robots.txt names the sitemap.
-
•
HTTPS certificate
The certificate could not be read from this platform, but the page was fetched over HTTPS.
-
•
Structured data Google accepts
Skipped — no structured data on the pages read.
-
•
Sitemap lists the live URLs
Skipped — no sitemap.
-
•
Sitemap dates
Skipped — no sitemap.
-
✓
Indexable by search engines
No noindex on the page or in the headers, and robots.txt lets Googlebot in.
-
✓
HSTS header
Strict-Transport-Security is set — browsers remember to use HTTPS.
-
✓
Mixed content
Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.
-
✓
Missing pages return 404
A made-up URL returns 404, so Google never indexes ghost pages.
-
✓
HTTP redirects to HTTPS
http:// redirects (301) to https://route3shop.com/.
-
✓
Internal links resolve
All 10 internal links read on the home page answer.
-
✓
Language declared
<html lang="en">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
robots.txt
robots.txt is served (1 group).
-
✓
www and apex agree
www.route3shop.com redirects (302) to route3shop.com.
-
✓
Lighthouse SEO score
Lighthouse SEO 100/100.
-
✓
Lighthouse best practices
Lighthouse best practices 100/100.
On-page SEO & content 14 of 25 points
-
✗
Single H1
No H1 heading on the page — the one line that says what the page is about.
What we’d do: Every page gets one H1 that names the service and the place.
-
!
Page title
“Affordable Used & Refurbished Appliances — Route 3 Liquidation” is 62 characters. Google shows about 60 and cuts the rest, so the end of it is lost in results.
What we’d do: We write titles of 30–60 characters, the topic first and the brand last, so nothing is cut.
-
!
Meta description
163 characters. Google shows about 160 and cuts the rest with an ellipsis.
What we’d do: We write descriptions of 120–160 characters, the point first.
-
!
About and privacy pages
The home page links a privacy policy but no About page. Google's quality raters are told to find out who is behind a site; an About page with the owner's name, the crew and the years is where a business answers that.
What we’d do: An About page with the owner and the crew by name, their photos and roles, and a privacy policy, both linked from every page's footer.
-
•
Titles across the site
Skipped — no inner page read.
-
•
Descriptions across the site
Skipped — no inner page read.
-
•
Pages that repeat each other
Skipped — no inner page read.
-
•
Canonical and share card on every page
Skipped — no inner page read.
-
•
Pictures named and described for what they show
No pictures on the pages read.
-
•
Title and H1 differ
Skipped — no title or no H1 to compare.
-
•
Titles lead with the subject
Skipped — no inner page read.
-
•
Service pages link each other
Skipped — no service page read.
-
•
Pages read
No sitemap to pick inner pages from, so the home page stands for the site.
-
•
Article schema on the post
Skipped — no post found in the sitemap.
-
✓
Social share cards
Open Graph title and image and a Twitter card with its own image. A share on any platform unfurls with a picture.
-
✓
No stock phrases
None of the phrases copy falls back on when it has no facts (“look no further”, “we pride ourselves”, “one-stop shop”, a run of “top-notch” and “peace of mind”) on the 1 page read.
-
✓
No placeholder or template text
No template or placeholder text on the 1 page read — no lorem ipsum, sample address or number, “add your text here”, or “undefined” where a value should be.
-
✓
No stock or AI-marked pictures
None of the 2 pictures on the pages read is marked as bought stock or AI-made — not by where it is served from, its name, its alt text.
-
✓
Not a stock template
No builder or stock theme shows in the page: no template credit, demo pictures or sample text.
-
✓
Image alt text
All 7 images have an alt attribute.
-
✓
Readable content in the HTML
329 words of readable text in the HTML.
-
✓
Share image loads
The share image loads (image/png, 292 KB).
-
✓
A page for each service
6 service pages linked from the home page (no sitemap to read) (/delivery-services, /furniture-more?q=&category=&max=&sort=newest&page=1, /pickup, …).
-
✓
Favicon
A favicon is linked — it shows in the tab and beside the site in Google's results.
-
✓
A menu a thumb can use
6 links in the header and menu.
AI search / AEO / GEO readiness 4 of 35 points
-
✗
FAQPage schema
No FAQ — not in the schema and not on the page. Question-and-answer blocks are what the answer engines lift most readily.
What we’d do: Every substantive page carries a visible FAQ with FAQPage schema built from the same text.
-
✗
llms.txt
No llms.txt at the site root. ChatGPT, Claude and Perplexity have to piece the business together from the pages.
What we’d do: Every site ships an llms.txt written from its facts: who, what, where, the proof, the pages.
-
✗
Questions answered on the page
No question is asked and answered on the 1 page read. When someone asks ChatGPT or Google's AI about a service, the engines quote pages that ask that question and answer it in a sentence or two.
What we’d do: Every service page answers the questions people ask about that service — four or more, each asked as a heading and answered in its first sentence — with FAQPage schema from the same text.
-
✗
JSON-LD present and valid
No JSON-LD on the page. Google and the answer engines get no structured statement of what this is.
What we’d do: Every page carries Organization or LocalBusiness, WebSite, BreadcrumbList and the page's own type.
-
✗
The first paragraph answers
The home page has no H1 to answer under. An answer engine quotes the sentence right under the heading.
What we’d do: The first paragraph under the headline answers the question the page is for — what, where, for whom — in two or three sentences, so a searcher sees it without scrolling and an engine can lift it whole.
-
!
Extractable structure
Little for an engine to lift: 8 H2s, 2 H3s, 3 list items. Answer engines quote headed sections, lists and question-and-answer blocks.
What we’d do: Every page is written in headed sections with lists and question headings, so an answer can be lifted whole.
-
•
FAQ questions visible on the page
Skipped — no FAQ schema to compare.
-
•
FAQs on the inner pages
Skipped — no inner page read.
-
•
Specifics an engine can cite
Skipped — no service page or post read to hold to the competitor test.
-
•
Schema on the inner pages
Skipped — no inner page read.
-
•
Freshness dates in schema
No dateModified or datePublished in the schema. Not expected on every home page; a freshness date helps the engines trust the page is current.
-
•
Speakable specification
No speakable specification. Google's speakable is a news-only beta, so this is noted, not scored.
-
✓
Readable without JavaScript
The page's 329 words are in the HTML the server sends, so a crawler that runs no JavaScript reads them.
-
✓
AI answers may quote the page
Nothing on the page stops an answer engine from quoting it: no nosnippet, max-snippet limit, noarchive or noai.
-
✓
AI crawlers allowed
robots.txt lets every answer engine in: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User and the rest. GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot each get the home page from the edge, as a browser does.
Local SEO & entity signals 0 of 5 points
-
✗
Business entity schema
No Organization or LocalBusiness schema. The engines have no entity to attach the reviews, the phone and the service area to.
What we’d do: LocalBusiness (or the trade's own type) with name, phone, address, hours, service area and sameAs on every page.
-
✗
Service area stated by town
The home page does not say which towns the business serves — visitors and engines both need it.
What we’d do: The towns the business works in, named — a service-area line in the footer of every page and areaServed in the schema with each town — so a search from any of them finds it.
-
✗
Linked to its profiles
Nothing ties this site to the business's profiles elsewhere: no sameAs in the schema, and no link to a Google Business Profile, Facebook or Yelp page. Those links are how the engines tell this business from others with a similar name.
What we’d do: The business node's sameAs lists every real profile — the Google Business Profile first, then Facebook, Yelp, BBB and the trade's own directories — and the footer links to them.
-
✗
Trust signals
No insurance, guarantee, license or accreditation language on the home page. Noted, not scored.
What we’d do: Insurance, a written guarantee and the trade's credentials, stated plainly where the visitor decides.
-
!
Site name for Google
Nothing names the site: no WebSite schema and no og:site_name, so Google picks the name shown above each result from the title and headings.
What we’d do: WebSite schema on the home page with the business's name, and alternateName for any other name people use, as on the Business Profile.
-
!
Reviews on the page
Reviews are quoted but there is no rating or count beside them, and nothing says how many there are.
What we’d do: The Google rating and count, three or more reviews quoted word for word with the reviewer's first name, and a link to the profile they live on — in the HTML, so the engines read them too.
-
!
Hours shown and in schema
The hours are on the page but not in the business schema, so the engines read them out of the prose.
What we’d do: The hours on every page, in the footer or beside the number, and the same hours in openingHoursSpecification, as the Business Profile shows them.
-
•
Business schema completeness
Skipped — no business node to read.
-
•
The trade's own schema type
Skipped — no business node to read.
-
•
A named person
No named person in the schema. Not required: a home-service company is known by its brand, and the business node carries what the engines tie the reviews and the pages to. A Person belongs on the About page only when the owner wants to be named.
-
✓
Address and phone on the page
The phone ((618) 772-4948) and where the business is (Red Bud, Illinois) are on the page as text.
Speed, scripts & mobile 13 of 20 points
-
✗
Compression
The HTML is sent uncompressed — three to five times more bytes than it needs.
What we’d do: Brotli or gzip on every text response; every host we use does it by default.
-
✗
Page weight
6.4 MB downloaded to show the home page on a phone. On a cellular connection that is many seconds before the page settles.
What we’d do: Our pages weigh 300–700 KB in all: 20–50 KB of HTML, two fonts, pictures sized to the box they fill in WebP or AVIF, and almost no JavaScript.
-
!
Nothing blocks the first paint
2 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.8 s of the first paint on waiting for them.
What we’d do: The styles the first screen needs are inlined and the rest load after it, every script is deferred, and the hero image is preloaded: nothing stands between the HTML and the first paint.
-
!
Readable and tappable on a phone
2 buttons or links are too small or too close to others to tap reliably (“Show slide 2: Free appliance pickup”, “Show slide 3: Furniture & more”).
What we’d do: Every word clears WCAG AA contrast — 4.5:1, or 3:1 for large text — measured as rendered at phone and desktop widths, and every button and link is at least 44 pixels square with room around it.
-
!
Image hygiene
7 images: 7 with dimensions, 0 in a modern format or through an image service, 4 lazy-loaded. none are WebP or AVIF, which are half the size of JPEG and PNG.
What we’d do: Every image has width and height, is served as WebP or AVIF at the size it is shown, and loads lazily below the fold.
-
!
Time to first byte
First byte took 1156 ms from our server. Google's guidance is under 800 ms; everything on the page waits for this.
What we’d do: Static pages served from an edge network answer in well under half a second.
-
•
Interaction to Next Paint (INP)
No real-user INP yet — Google reports it once a page has enough visitors on Chrome. It measures how quickly the page reacts to a tap.
-
✓
Mobile viewport
The viewport meta tag is set for phones.
-
✓
No popup on arrival
Nothing covers the page on arrival: no popup, no email gate.
-
✓
Mobile PageSpeed score
Lighthouse mobile performance 99/100. Google's own bands: 90 and up is good, 50–89 needs improvement.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 93/100.
-
✓
Scripts and third parties
46 scripts, 275 KB of JavaScript, from no third party.
-
✓
No hero slider or autoplay video
One hero: no slider and no autoplaying video in the first screen.
-
✓
Cumulative Layout Shift (CLS)
Cumulative Layout Shift 0.00 (lab). Google's thresholds: 0.1 good, 0.25 poor.
-
✓
Fonts
3 font files (62 KB) from Google Fonts.
-
✓
The hero image loads first
The largest thing on the first screen is text or a styled block (<h2 class="text-4xl font-bold leading-tight sm:text-5xl">), which paints as soon as the HTML arrives.
-
✓
Pinch-to-zoom allowed
Pinch-to-zoom is allowed.
-
✓
No fixed-width overflow
No inline widths of 400px or more that would push past a phone screen.
-
✓
HTML weight
About 13 KB compressed (62 KB of HTML).
-
✓
HTTP/2 or HTTP/3
HTTP/2 — Google's PageSpeed test loaded the page over it (this scan cannot read the protocol itself).
-
✓
One chat widget at most
No chat widget scripts on the page.
-
✓
Largest Contentful Paint (LCP)
Largest Contentful Paint 1.5 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).
-
✓
Static files cached
Every static file is served with a long cache lifetime.
-
✓
What would speed it up most
Nothing large left to fix. PageSpeed's remaining suggestions: Render-blocking requests (about 0.8 s).
Conversion & lead generation 2 of 5 points
-
!
Contact form
No form on the home page; a contact or quote page is linked. Every extra tap loses a share of visitors.
What we’d do: Our home pages carry the quote form itself — name, phone, what they need — stored before it is emailed, so nothing is lost.
-
!
Analytics installed
No analytics tag found — nothing counts the visits, the calls or the forms, so nothing can be improved on evidence.
What we’d do: First-party traffic logging on every site, and GA4 as the second source.
-
•
Lead form wiring
No form in the home page's HTML to read — a form a script draws in the browser can't be read from outside.
-
•
A lead form that fits a phone
No form on the home page to read; the contact form check says whether one is linked.
-
•
Chat or text option
No chat or text option. Not a fault, but a share of visitors will not call; an assistant that answers in seconds, day and night, is the cheapest lead a site can add.
-
✓
Call to action in the first screen
A phone link, a form or a quote button appears in the top of the page.
-
✓
Tappable phone number
3 tel: links — the number dials from a phone.
-
✓
No CAPTCHA puzzle
No CAPTCHA puzzle on the page.
Want these fixed?
Every fix above is part of the work Zorva Labs does. Tell us the business and what you want from the site, and a written, priced proposal comes back in one business day.
We can fix every issue on route3shop.com.
Zorva Labs builds, hosts and grows websites for businesses across the United States — including the fixes flagged above. Every engagement is priced to the project, with a written proposal in one business day.