Search the site · Ask Zorva

Results appear as you type. Press Enter and Zorva answers from this site’s own pages.

Public scan result · scored by the Zorva Labs website scan

shopsmartmarketing.com scored 40/100 on the website scan.

Needs work

shopsmartmarketing.com · Scanned 2026-11-10

58 passed18 warnings17 failed

  • Technical SEO & indexability9 of 10 points
  • On-page SEO & content13 of 25 points
  • AI search / AEO / GEO readiness6 of 35 points
  • Local SEO & entity signals2 of 5 points
  • Speed, scripts & mobile7 of 20 points
  • Conversion & lead generation3 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

  • ✗

    AI crawlers allowed +1 point

    robots.txt lets every answer engine in: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User and the rest. The host refuses GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot at the edge (403 each, while a browser gets the page): those engines can't read the site even though robots.txt allows them.

    What we’d do: The host's firewall and bot rules let in every crawler robots.txt allows, GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot among them.

  • ✗

    FAQPage schema +3 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 +3 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 +3 points

    Only 2 questions asked and answered on the pages read (2 on the service page). Answer engines quote pages that ask the customer's 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.

  • !

    FAQs on the inner pages +3 points

    The service page answers questions without FAQPage schema.

    What we’d do: Every service, area and post page carries its own researched questions — four or more, the ones people ask about that subject, none repeated from another page — visible and in FAQPage schema.

Every check, by category (103 checks)

Technical SEO & indexability 9 of 10 points

  • ✗

    Security headers

    Missing 4 of the four baseline security headers: Content-Security-Policy, X-Content-Type-Options, frame protection (X-Frame-Options or CSP frame-ancestors), Referrer-Policy.

    What we’d do: Content-Security-Policy, X-Content-Type-Options, frame protection and Referrer-Policy on every response.

  • •

    HTTPS certificate

    The certificate could not be read from this platform, but the page was fetched over HTTPS.

  • •

    www and apex agree

    www.shopsmartmarketing.com answered 526.

  • ✓

    Indexable by search engines

    No noindex on the page or in the headers, and robots.txt lets Googlebot in.

  • ✓

    Structured data Google accepts

    7 schema types on the 2 pages read, and nothing Google would reject: ratings only where they belong and shown on the page, every reference typed, every value filled.

  • ✓

    Canonical URL

    Canonical is https://shopsmartmarketing.com/.

  • ✓

    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.

  • ✓

    Sitemap

    Sitemap at https://shopsmartmarketing.com/sitemap.xml — an index of 2 sitemaps.

  • ✓

    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://shopsmartmarketing.com/.

  • ✓

    Internal links resolve

    All 10 internal links read on the home page answer.

  • ✓

    Language declared

    <html lang="en-US">.

  • ✓

    Redirect chain

    The URL answers directly, with no redirect.

  • ✓

    robots.txt

    robots.txt is served (1 group, 2 sitemap lines).

  • ✓

    Sitemap named in robots.txt

    robots.txt names the sitemap: https://shopsmartmarketing.com/sitemap.xml.

  • ✓

    Sitemap lists the live URLs

    The sitemap's 27 URLs are all on https://shopsmartmarketing.com, and the pages read from it answer directly and are open to indexing.

  • ✓

    Lighthouse SEO score

    Lighthouse SEO 92/100.

  • ✓

    Lighthouse best practices

    Lighthouse best practices 100/100.

  • ✓

    Sitemap dates

    27 pages with lastmod dates, from 2024-09-19 to 2026-08-17.

On-page SEO & content 13 of 25 points

  • ✗

    Page title

    “ShopSmart Marketing – Connecting Local Businesses To Your Ideal Clients” is 71 characters — a third of it is cut in search results.

    What we’d do: We write titles of 30–60 characters, the topic first and the brand last.

  • ✗

    Meta description

    399 characters — the last third is cut in results.

    What we’d do: We write descriptions of 120–160 characters, the point first.

  • ✗

    No placeholder or template text

    The home page shows lorem ipsum; the service page shows lorem ipsum. Left on a live page, it tells every visitor nobody finished the site.

    What we’d do: Nothing ships with a placeholder in it: every value comes from the business's own facts, and the build fails a page that still carries one.

  • ✗

    Descriptions across the site

    the service page's description is 357 characters.

    What we’d do: Every page gets its own 120–160 character description, checked in the build.

  • !

    Not a stock template

    Built with WordPress, the Hello Elementor theme and Elementor: Hello Elementor is a stock theme thousands of sites run, most of them from the same starter layouts.

    What we’d do: A site designed for this business — its own layout, type and colors, written from its own facts — with nothing left of whatever it was built from.

  • !

    Service pages link each other

    The service page read links one other service page in its copy (/social-media/), of 20.

    What we’d do: Every service page names the related services in its own copy — the repair page links the replacement page, the inspection page the repair — so a visitor and a crawler move between them without the menu.

  • !

    A menu a thumb can use

    The service page read (/services/) is not linked from the home page.

    What we’d do: A menu of five to eight items a thumb can hit — the services, the area, about, contact — with the number beside it, and every service page one tap from the home page.

  • •

    Pages read

    Read with the home page: service page https://shopsmartmarketing.com/services/.

  • •

    Article schema on the post

    No post found in the sitemap to check.

  • ✓

    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.

  • ✓

    Titles across the site

    Each page read has its own title of 30–60 characters.

  • ✓

    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 2 pages read.

  • ✓

    No stock or AI-marked pictures

    None of the 4 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, or the credits inside the 3 files opened.

  • ✓

    Single H1

    One H1: “Targeted Marketing Services To Help Your Business Grow”.

  • ✓

    Image alt text

    All 6 images have an alt attribute.

  • ✓

    Readable content in the HTML

    642 words of readable text in the HTML.

  • ✓

    Share image loads

    The share image loads (image/png, 285 KB).

  • ✓

    Pages that repeat each other

    The pages read share few sentences: at most 1 of 11 (9%) between the service and home pages.

  • ✓

    Canonical and share card on every page

    The inner page read names itself as its canonical, carries a share image and a Twitter card, and has one H1.

  • ✓

    Pictures named and described for what they show

    3 of the 3 pictures on the pages read are named and described for what they show.

  • ✓

    A page for each service

    20 service pages in the sitemap (/magazine-services/, /post-card-services/, /social-media/, …).

  • ✓

    Favicon

    A favicon is linked — it shows in the tab and beside the site in Google's results.

  • ✓

    Title and H1 differ

    The title and the H1 are different, each doing its own job.

  • ✓

    About and privacy pages

    The home page links an About page (/about/) and a privacy policy (/privacy-policy/).

  • ✓

    Titles lead with the subject

    The inner pages' titles lead with their subject, not the business name.

AI search / AEO / GEO readiness 6 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.

  • ✗

    AI crawlers allowed

    robots.txt lets every answer engine in: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User and the rest. The host refuses GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot at the edge (403 each, while a browser gets the page): those engines can't read the site even though robots.txt allows them.

    What we’d do: The host's firewall and bot rules let in every crawler robots.txt allows, GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot among them.

  • ✗

    The first paragraph answers

    The home page's first paragraph does not say what its headline is about; the service page's headline is followed by buttons and pictures, not a sentence. 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.

  • !

    Questions answered on the page

    Only 2 questions asked and answered on the pages read (2 on the service page). Answer engines quote pages that ask the customer's 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.

  • !

    FAQs on the inner pages

    The service page answers questions without FAQPage schema.

    What we’d do: Every service, area and post page carries its own researched questions — four or more, the ones people ask about that subject, none repeated from another page — visible and in FAQPage schema.

  • !

    Specifics an engine can cite

    The service page (/services/): 662 words, 1 number, 1 name (Toggle) — thin for a page an answer engine should quote. They quote prices, timelines, counts, and named places, products and people.

    What we’d do: Every page is written from the business's own facts: real prices or ranges, timelines, how many and how big, the products and brands used, the towns and neighborhoods worked in, the people by name — 300 words or more that no competitor could publish unchanged.

  • !

    Schema on the inner pages

    The service page (/services/) has nothing naming the business and no Service for what it offers.

    What we’d do: Every page carries the business node, a BreadcrumbList and its own type — a Service on each service page, BlogPosting on each post — so an engine knows what each page is and whose it is.

  • •

    FAQ questions visible on the page

    Skipped — no FAQ schema to compare.

  • •

    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 642 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.

  • ✓

    JSON-LD present and valid

    5 schema types: Organization, ImageObject, WebSite, SearchAction, EntryPoint.

  • ✓

    Extractable structure

    Structure an engine can lift: 17 H2s, 3 H3s, 45 list items.

Local SEO & entity signals 2 of 5 points

  • ✗

    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.

  • ✗

    The trade's own schema type

    Organization only: it says a company exists, not what it does or where.

    What we’d do: The business node uses schema.org's own type for the trade — RoofingContractor, Plumber, HVACBusiness, Electrician, HousePainter, GeneralContractor, MovingCompany, Locksmith and the rest under HomeAndConstructionBusiness and LocalBusiness — so the engines file it under what it does, not only that it exists.

  • ✗

    Hours shown and in schema

    No hours on the home page or in the schema. “Are they open now?” is the first thing map search and a visitor want to know.

    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

    The business node has name, url, logo or image but not telephone, address.

    What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.

  • !

    Trust signals

    Only since <year>, 10 years. Noted, not scored: a visitor comparing three sites reads whether the work is insured and guaranteed.

    What we’d do: Insurance, a written guarantee and the trade's credentials, stated plainly where the visitor decides.

  • !

    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.

  • •

    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.

  • ✓

    Business entity schema

    Organization schema names the business.

  • ✓

    Address and phone on the page

    The phone ((234) 567-8910) and where the business is (1234 Road) are on the page as text.

  • ✓

    Site name for Google

    WebSite schema names the site “ShopSmart Marketing” — the name Google shows above each result.

Speed, scripts & mobile 7 of 20 points

  • ✗

    Scripts and third parties

    28 scripts, 984 KB of JavaScript, from 4 third parties (Google Tag Manager, s0.wp.com, stats.wp.com and Google Ads). Google Tag Manager 0.4 s held the phone's main thread while the page loaded. A phone downloads, parses and runs all of it before the page settles.

    What we’d do: Our pages load one analytics tag and the form's bot check — two third parties and under 100 KB of JavaScript — and nothing runs before the page is drawn.

  • ✗

    Nothing blocks the first paint

    49 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 2.3 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.

  • ✗

    Largest Contentful Paint (LCP)

    Largest Contentful Paint 11.0 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).

    What we’d do: The hero image sized and preloaded, no render-blocking scripts, a fast first byte: our pages paint in about a second.

  • ✗

    Page weight

    3.9 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.

  • !

    Mobile PageSpeed score

    Lighthouse mobile performance 67/100. Google calls 50–89 “needs improvement”; lab runs vary, so we grade 70 and up as a pass.

    What we’d do: Our sites score 90 and up on mobile: static HTML from an edge network, images sized and in modern formats, almost no JavaScript.

  • !

    Image hygiene

    6 images: 6 with dimensions, 0 in a modern format or through an image service, 1 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.

  • !

    Fonts

    6 font files (219 KB) from shopsmartmarketing.com.

    What we’d do: Two font families in the weights the page uses, from one host, with font-display set so the words show at once in a fallback face.

  • !

    The hero image loads first

    The hero image is not preloaded or marked high priority, so the browser finds it late.

    What we’d do: The hero picture is the first thing the HTML asks for: sized, in a modern format, preloaded with fetchpriority=high and never lazy-loaded, so the first screen paints in about a second.

  • !

    Readable and tappable on a phone

    One piece of text is too faint to read against its background (“Find Local Offers!” 2.93:1); WCAG asks 4.5:1 for text that size.

    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.

  • !

    What would speed it up most

    PageSpeed's biggest savings on this page: Improve image delivery (about 4.5 s); Render-blocking requests (about 2.3 s); Reduce unused JavaScript (about 1.0 s).

    What we’d do: These are the first three things we would fix.

  • •

    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.

  • ✓

    Lighthouse accessibility score

    Lighthouse accessibility 91/100.

  • ✓

    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.05 (lab). Google's thresholds: 0.1 good, 0.25 poor.

  • ✓

    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.

  • ✓

    Time to first byte

    First byte in 165 ms from our server.

  • ✓

    HTML weight

    About 31 KB compressed (177 KB of HTML).

  • ✓

    Compression

    Responses are compressed (br).

  • ✓

    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.

  • ✓

    Static files cached

    5 files served with a short or missing cache lifetime, 0 of them the site's own.

Conversion & lead generation 3 of 5 points

  • !

    Tappable phone number

    A phone number is shown but is not a tel: link — on a phone it has to be copied, not tapped.

    What we’d do: Every number on our sites is a tel: link, and every tap is counted as a lead.

  • !

    A lead form that fits a phone

    The lead form asks 6 fields; the phone field does not bring up the number keypad (type=tel). Every field costs a share of the people who start it.

    What we’d do: Name, phone, what they need: three to five fields, each labeled, the phone field a tel input so the keypad comes up, and one tap to send.

  • •

    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.

  • ✓

    Contact form

    2 forms on the home page.

  • ✓

    Call to action in the first screen

    A phone link, a form or a quote button appears in the top of the page.

  • ✓

    Lead form wiring

    The form posts to back to the page, where a script sends it (no spam guard shows in the page; a filter on the server can't be seen from outside).

  • ✓

    Analytics installed

    Measured by Google Tag Manager, Google Analytics.

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

Read with the home page: service page shopsmartmarketing.com/services/

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.

Want this fixed?

We can fix every issue on shopsmartmarketing.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.

ReplyOne business day
ProposalWritten · scoped · priced
ContractMonth to month
Proposal request

Tell us what you need

No spam · One business day reply · Month to month