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

paichtax.com scored 96/100 on the website scan.

Strong

paichtax.com · Scanned 2026-10-10

87 passed6 warnings1 failed

  • Technical SEO & indexability10 of 10 points
  • On-page SEO & content24 of 25 points
  • AI search / AEO / GEO readiness35 of 35 points
  • Local SEO & entity signals5 of 5 points
  • Speed, scripts & mobile19 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

  • !

    Contact form +2 points

    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.

  • !

    A page for each service +2 points

    Only 2 service pages in the sitemap (/tax-talk, /tax-talk/can-i-deduct-work-from-home-expenses). A service with no page of its own has nothing to rank for it.

    What we’d do: A page for every service the business sells, each with its own title, its own words, its own FAQ and Service schema, so a search for that service lands on the page about it and an engine can quote it.

  • !

    Static files cached +1 point

    4 files served with a short or missing cache lifetime, 3 of them the site's own. A return visitor downloads them 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.

Every check, by category (103 checks)

Technical SEO & indexability 10 of 10 points

  • !

    Sitemap dates

    Every page in the sitemap carries the same date (2026-10-09) — a build stamp, not the day each page changed. Google ignores dates it has learned not to trust.

    What we’d do: Each page's lastmod is the day its own content last changed, written from the content's hash, never the build date.

  • •

    HTTPS certificate

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

  • ✓

    Indexable by search engines

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

  • ✓

    Structured data Google accepts

    18 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://paichtax.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.

  • ✓

    Security headers

    All four baseline security headers are set.

  • ✓

    Sitemap

    Sitemap at https://paichtax.com/sitemap.xml — 9 URLs.

  • ✓

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

  • ✓

    Internal links resolve

    All 8 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 (7 groups, 1 sitemap line, the private paths repeated in each crawler's own group).

  • ✓

    Sitemap named in robots.txt

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

  • ✓

    www and apex agree

    www.paichtax.com redirects (301) to paichtax.com.

  • ✓

    Sitemap lists the live URLs

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

  • ✓

    Lighthouse SEO score

    Lighthouse SEO 100/100.

  • ✓

    Lighthouse best practices

    Lighthouse best practices 100/100.

On-page SEO & content 24 of 25 points

  • !

    A page for each service

    Only 2 service pages in the sitemap (/tax-talk, /tax-talk/can-i-deduct-work-from-home-expenses). A service with no page of its own has nothing to rank for it.

    What we’d do: A page for every service the business sells, each with its own title, its own words, its own FAQ and Service schema, so a search for that service lands on the page about it and an engine can quote it.

  • •

    Service pages link each other

    Skipped — fewer than three service pages to link between.

  • •

    Pages read

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

  • •

    Article schema on the post

    No post found in the sitemap to check.

  • ✓

    Page title

    “Paich & Co. Tax Services | CPA, Beaver County PA” — 48 characters, inside the 30–60 Google shows in full.

  • ✓

    Meta description

    155 characters — fills the space Google shows without being cut.

  • ✓

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

  • ✓

    Not a stock template

    No builder or stock theme shows in the page: no template credit, demo pictures or sample text.

  • ✓

    Single H1

    One H1: “Clear, Simple, Personal .”.

  • ✓

    Image alt text

    All 8 images have an alt attribute.

  • ✓

    Readable content in the HTML

    1,189 words of readable text in the HTML.

  • ✓

    Share image loads

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

  • ✓

    Descriptions across the site

    Each page read has its own description of 120–160 characters.

  • ✓

    Pages that repeat each other

    The pages read share no sentences beyond the header, footer and calls to action.

  • ✓

    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

    6 of the 7 pictures on the pages read are named and described for what they show (not: 1 with alt text that describes nothing (“Natalia Paich, CPA, CFP®, founder of Paich & Co. T…”, a string of keywords)).

  • ✓

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

  • ✓

    Titles lead with the subject

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

  • ✓

    A menu a thumb can use

    6 links in the header and menu, and the service page read is one tap from the home page.

AI search / AEO / GEO readiness 35 of 35 points

  • •

    Speakable specification

    No speakable specification. Google's speakable is a news-only beta, so this is noted, not scored.

  • ✓

    FAQPage schema

    FAQPage schema is present.

  • ✓

    FAQ questions visible on the page

    All 5 questions in the FAQ schema are on the page, with the answers it shows.

  • ✓

    llms.txt

    llms.txt is published (6 KB), headed with the name and linking 9 pages of the site — a plain statement of the business for the AI engines to read.

  • ✓

    Questions answered on the page

    11 questions asked and answered on the pages read (5 on the home page, 6 on the service page) — the shape an AI answer is lifted from.

  • ✓

    FAQs on the inner pages

    The inner page read carries its own FAQ with schema (5 questions on the service page), none repeated from another page.

  • ✓

    Specifics an engine can cite

    The service page (/services): 766 words, 15 numbers, 5 names (Social, Security, Solo, Form, …) — specifics only this business could publish, the kind an answer engine quotes.

  • ✓

    Schema on the inner pages

    The inner page read carries its own schema: the business and a BreadcrumbList, with a Service on the service page.

  • ✓

    Readable without JavaScript

    The page's 1,189 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

    17 schema types: AccountingService, LocalBusiness, Person, CollegeOrUniversity, PostalAddress, GeoCoordinates, AdministrativeArea, City, ….

  • ✓

    Freshness dates in schema

    Newest date in the schema: 2026-10-09.

  • ✓

    Extractable structure

    Structure an engine can lift: 9 H2s, 13 H3s, 29 list items.

  • ✓

    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.

  • ✓

    The first paragraph answers

    The first paragraph under the H1 answers in 28 words on the home page and 26 words on the service page.

Local SEO & entity signals 5 of 5 points

  • ✗

    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.

  • !

    Trust signals

    Only cpa, 25+ 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.

  • !

    Hours shown and in schema

    The hours are in the schema but nowhere a visitor reads them.

    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 entity schema

    AccountingService / LocalBusiness schema names the business.

  • ✓

    Service area stated by town

    The service area is stated by town: Beaver County, Pennsylvania, Allegheny County, Pennsylvania, Center Township and Chippewa and 13 more, in the schema too.

  • ✓

    Business schema completeness

    The business node carries name, url, telephone, address, logo or image, areaServed, openingHours.

  • ✓

    Linked to its profiles

    The business node's sameAs names Google Business Profile — the links the engines use to know this site and those profiles are one business.

  • ✓

    Address and phone on the page

    The phone ((724) 462-3079) and where the business is (Federal, PA) are on the page as text, and the phone matches the schema's.

  • ✓

    Site name for Google

    WebSite schema names the site “Paich & Co. Tax Services, LLC” — the name Google shows above each result.

  • ✓

    The trade's own schema type

    AccountingService: schema.org's own type for what the business does.

  • ✓

    A named person

    A named person in the schema: Natalia Paich.

Speed, scripts & mobile 19 of 20 points

  • !

    Static files cached

    4 files served with a short or missing cache lifetime, 3 of them the site's own. A return visitor downloads them 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.

  • •

    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.

  • ✓

    Readable and tappable on a phone

    Every piece of text Google's test measured on a phone clears WCAG AA contrast, and the buttons and links are big enough, and far enough apart, to tap.

  • ✓

    Mobile PageSpeed score

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

  • ✓

    Lighthouse accessibility score

    Lighthouse accessibility 94/100.

  • ✓

    Scripts and third parties

    4 scripts, 173 KB of JavaScript, from 2 third parties (static.cloudflareinsights.com and Google Tag Manager).

  • ✓

    Nothing blocks the first paint

    1 file loads before anything is drawn — styles and scripts in the head — and PageSpeed puts 0.2 s of the first paint on waiting for it.

  • ✓

    Image hygiene

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

  • ✓

    Fonts

    3 font files (109 KB) from paichtax.com.

  • ✓

    The hero image loads first

    The hero image is asked for early and not lazy-loaded (<img src="https://paichtax.com/assets/natalia-hero-desk-640.webp" srcs).

  • ✓

    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 71 ms from our server.

  • ✓

    HTML weight

    About 8 KB compressed (33 KB of HTML).

  • ✓

    Compression

    Compressed, as Google's PageSpeed test read the page from outside; this scan runs inside Cloudflare's network, where Cloudflare's compression never shows.

  • ✓

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

  • ✓

    Page weight

    361 KB downloaded to show the home page on a phone.

  • ✓

    What would speed it up most

    Nothing large left to fix. PageSpeed's remaining suggestions: Improve image delivery (about 0.1 s).

Conversion & lead generation 3 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.

  • •

    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.

  • ✓

    Analytics installed

    Measured by Google Analytics.

  • ✓

    Tappable phone number

    4 tel: links — the number dials from a phone.

  • ✓

    No CAPTCHA puzzle

    No CAPTCHA puzzle on the page.

Read with the home page: service page paichtax.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 paichtax.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