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

livinglocal-mag.com scored 30/100 on the website scan.

Major issues

livinglocal-mag.com · Scanned 2026-10-21

43 passed21 warnings22 failed

  • Technical SEO & indexability6 of 10 points
  • On-page SEO & content8 of 25 points
  • AI search / AEO / GEO readiness3 of 35 points
  • Local SEO & entity signals0 of 5 points
  • Speed, scripts & mobile11 of 20 points
  • Conversion & lead generation2 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 +4 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.

  • ✗

    Questions answered on the page +4 points

    No question is asked and answered on the 2 pages 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.

  • ✗

    FAQs on the inner pages +4 points

    The service page read carries no FAQ. The questions people ask about a service are what the answer engines quote.

    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.

  • !

    llms.txt +3 points

    llms.txt is published (1 KB) but links only 2 pages of the site. The format is a heading with the name, a summary, then the pages worth reading, each linked, so an engine knows where to look.

    What we’d do: Every site ships an llms.txt written from its facts — who, what, where, the proof — with a link to every service, area and post page, rewritten when the pages change.

  • ✗

    Meta description +2 points

    The home page has no meta description, so Google writes its own from the page.

    What we’d do: Every page gets a 120–160 character description written to earn the click.

Every check, by category (103 checks)

Technical SEO & indexability 6 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.

  • !

    HSTS header

    No Strict-Transport-Security header. Browsers still use HTTPS, but a first visit typed without it can be intercepted.

    What we’d do: HSTS with a one-year max-age on every response.

  • !

    Missing pages return 404

    A made-up URL redirects (301) instead of returning 404. Better than a soft 404, but a redirect to the home page still teaches Google the site has no missing pages.

    What we’d do: Missing routes return a real 404 with a helpful page.

  • !

    robots.txt

    robots.txt is served, but OAI-SearchBot, ChatGPT-User, GPTBot and PerplexityBot and others have groups of their own that don't repeat the * group's Disallow: /wp-admin/. A crawler named in its own group follows only that group, so they may read what the site keeps from every other crawler.

    What we’d do: Every group in robots.txt repeats the private paths, so a crawler named on its own is kept out of them too.

  • !

    Lighthouse SEO score

    Lighthouse SEO 85/100 — the report names what to fix.

    What we’d do: Our sites score 100 on Lighthouse SEO: every page crawlable, titled, described, with valid links and alt text.

  • •

    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.

  • ✓

    Indexable by search engines

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

  • ✓

    Canonical URL

    Canonical is https://livinglocal-mag.com/.

  • ✓

    Mixed content

    Every script, stylesheet, image, frame and form on the page is loaded over HTTPS.

  • ✓

    Sitemap

    Sitemap at https://livinglocal-mag.com/wp-sitemap.xml — an index of 2 sitemaps.

  • ✓

    HTTP redirects to HTTPS

    http:// redirects (301) to https://livinglocal-mag.com/.

  • ✓

    Internal links resolve

    All 11 internal links read (10 on the home page, 1 in llms.txt) answer.

  • ✓

    Language declared

    <html lang="en-US">.

  • ✓

    Redirect chain

    The URL answers directly, with no redirect.

  • ✓

    Sitemap named in robots.txt

    robots.txt names the sitemap: https://livinglocal-mag.com/wp-sitemap.xml.

  • ✓

    www and apex agree

    www.livinglocal-mag.com redirects (301) to livinglocal-mag.com.

  • ✓

    Sitemap lists the live URLs

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

  • ✓

    Lighthouse best practices

    Lighthouse best practices 100/100.

  • ✓

    Sitemap dates

    9 pages with lastmod dates, from 2023-01-11 to 2026-05-29.

On-page SEO & content 8 of 25 points

  • ✗

    Meta description

    The home page has no meta description, so Google writes its own from the page.

    What we’d do: Every page gets a 120–160 character description written to earn the click.

  • ✗

    Social share cards

    No Open Graph or Twitter card tags. A share in Messages, LinkedIn, Facebook or Slack shows a bare link.

    What we’d do: Every page carries og:title, og:image, twitter:card and twitter:image, with a real picture.

  • ✗

    Descriptions across the site

    the service page has no description.

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

  • ✗

    Service pages link each other

    The service page read links none of the other 4 service pages in its copy. Each stands alone, so nothing moves between them but the menu.

    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.

  • !

    Page title

    “Living Local Magazine” is only 21 characters. There is room for the service and the place, which is what people search.

    What we’d do: We write titles of 30–60 characters with the service, the place and the name.

  • !

    Readable content in the HTML

    193 words of readable text on the home page — thin for a page that has to explain a business.

    What we’d do: Home pages we write carry the services, the places, the proof and the questions people ask.

  • !

    Canonical and share card on every page

    The service page (/advertising) has no share image and no Twitter card.

    What we’d do: Every page names itself as its canonical, carries its own og:image and twitter:image, and opens with one H1 — checked on every page before the site ships.

  • !

    Not a stock template

    Built with WordPress, the Neve theme and Elementor: Neve 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.

  • !

    About and privacy pages

    The home page links an About page (/about-us) but no privacy policy — a site whose form takes names, phone numbers and emails says what it does with them.

    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.

  • !

    A menu a thumb can use

    The service page read (/advertising) 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.

  • •

    Share image loads

    Skipped — no og:image to fetch.

  • •

    Pages that repeat each other

    Not enough copy on the pages read to compare.

  • •

    Titles lead with the subject

    No business name in the schema to compare the titles against.

  • •

    Pages read

    Read with the home page: service page https://livinglocal-mag.com/advertising.

  • •

    Article schema on the post

    No post found in the sitemap to check.

  • ✓

    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 placeholder or template text

    No template or placeholder text on the 2 pages 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 6 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 6 files opened.

  • ✓

    Single H1

    One H1: “Local Living Magazine Home”.

  • ✓

    Image alt text

    All 7 images have an alt attribute.

  • ✓

    Pictures named and described for what they show

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

  • ✓

    A page for each service

    5 service pages in the sitemap (/advertising, /advertising/local-living-magazine, /advertising/pop-out-inserts, …).

  • ✓

    Favicon

    No favicon link, but /favicon.ico is served — browsers and Google find it there.

  • ✓

    Title and H1 differ

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

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

  • ✗

    Questions answered on the page

    No question is asked and answered on the 2 pages 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.

  • ✗

    FAQs on the inner pages

    The service page read carries no FAQ. The questions people ask about a service are what the answer engines quote.

    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 (/advertising) gives no number — no price, timeline, size or count — and names nothing beyond the business and its town. A competitor could publish it unchanged, and the answer engines quote pages with specifics they can check.

    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 (/advertising) has no structured data. Past the home page the engines get no structured statement of what a page is or whose it is.

    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.

  • ✗

    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.

  • !

    llms.txt

    llms.txt is published (1 KB) but links only 2 pages of the site. The format is a heading with the name, a summary, then the pages worth reading, each linked, so an engine knows where to look.

    What we’d do: Every site ships an llms.txt written from its facts — who, what, where, the proof — with a link to every service, area and post page, rewritten when the pages change.

  • !

    AI crawlers allowed

    robots.txt blocks CCBot (Common Crawl (training data for many models)). A defensible choice for training data, but every answer engine is allowed. GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot each get the home page from the edge, as a browser does.

    What we’d do: We block nothing an answer engine reads.

  • !

    The first paragraph answers

    The service page's headline is followed by buttons and pictures, not a sentence.

    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.

  • •

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

  • ✓

    Extractable structure

    Structure an engine can lift: 6 H2s, 4 H3s, 18 list items.

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.

  • ✗

    Address and phone on the page

    Neither a phone number nor a town or street address is on the home page as text. Map search and the answer engines match a business to a place by what its pages say.

    What we’d do: The business name, phone and town — or street address — in the footer of every page, exactly as the Google Business Profile has them, and the same in the schema.

  • ✗

    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.

  • ✗

    Reviews on the page

    No reviews, rating or testimonials on the home page, and no link to a profile that has them — the proof visitors look for first.

    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

    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.

  • !

    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.

  • •

    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.

Speed, scripts & mobile 11 of 20 points

  • ✗

    Nothing blocks the first paint

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

  • ✗

    Time to first byte

    First byte took 2.8 s from our server — the page cannot be fast if the server is slow to start.

    What we’d do: Static pages served from an edge network answer in well under half a second.

  • ✗

    Static files cached

    62 files served with a short or missing cache lifetime, 62 of them the site's own. Every visit downloads the site again.

    What we’d do: Every static file — styles, scripts, fonts, pictures — is served with a year-long cache header and a fingerprinted name, so a return visit downloads only the HTML.

  • !

    Fonts

    3 font files (222 KB) from livinglocal-mag.com. 3 faces without font-display, so the words wait for the file.

    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

    4 pieces of text are too faint to read against their background (“LEARN MORE” 3.17: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.

  • !

    Page weight

    1.7 MB downloaded to show the home page on a phone. On a cellular connection that is seconds of waiting, and data the visitor pays for.

    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.

  • !

    What would speed it up most

    PageSpeed's biggest savings on this page: Render-blocking requests (about 1.9 s); Use efficient cache lifetimes (about 1.1 s); Font display (about 0.6 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.

  • ✓

    Mobile PageSpeed score

    Lighthouse mobile performance 92/100. Google's own bands: 90 and up is good, 50–89 needs improvement.

  • ✓

    Lighthouse accessibility score

    Lighthouse accessibility 92/100.

  • ✓

    Scripts and third parties

    21 scripts, 222 KB of JavaScript, from no third party.

  • ✓

    Image hygiene

    7 images: 7 with dimensions, 6 in a modern format or through an image service, 4 lazy-loaded.

  • ✓

    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.

  • ✓

    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 17 KB compressed (92 KB of HTML).

  • ✓

    Compression

    Responses are compressed (gzip).

  • ✓

    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 2.1 s in the lab (no real-user data yet; lab runs vary, so we pass up to 4 s).

Conversion & lead generation 2 of 5 points

  • ✗

    Tappable phone number

    No phone number on the home page. For a service business the call is the conversion.

    What we’d do: A tappable number in the header, the hero and the footer of every page.

  • !

    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.

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

Read with the home page: service page livinglocal-mag.com/advertising

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 livinglocal-mag.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