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

taylortaxandfinancial.com scored 35/100 on the website scan.

Major issues

taylortaxandfinancial.com · Scanned 2026-11-09

54 passed23 warnings17 failed

  • Technical SEO & indexability7 of 10 points
  • On-page SEO & content8 of 25 points
  • AI search / AEO / GEO readiness6 of 35 points
  • Local SEO & entity signals2 of 5 points
  • Speed, scripts & mobile8 of 20 points
  • Conversion & lead generation4 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.

  • ✗

    llms.txt +4 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 +4 points

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

    Neither inner page read carries a 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.

  • ✗

    Page title +2 points

    “IRS Wage Levy and Bank Levy Help | Taylor Tax & Financial | Taylor Tax & Financial Consult…” is 97 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.

Every check, by category (103 checks)

Technical SEO & indexability 7 of 10 points

  • !

    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.

  • !

    Security headers

    Missing: Referrer-Policy.

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

  • !

    Internal links resolve

    /www.calendly.com/taylor-tax-financial/new-tax-client (404) answers with an error, of the 21 internal links read on the home page.

    What we’d do: Every internal link points at a page that exists: the build checks each one before it ships, and a page that moves gets a 301 from its old address.

  • !

    Lighthouse best practices

    Lighthouse best practices 77/100 — the report names what to fix.

    What we’d do: No console errors, no deprecated APIs, images at their real aspect ratio, HTTPS everywhere.

  • !

    Sitemap lists the live URLs

    The post page it lists (/blog/blog-content) redirects to /preview/site/taylor-tax-financial-consulting-inc-686d3a6a916ff/blog.

    What we’d do: The sitemap is written from the pages themselves on every build: only final, indexable https URLs, on the one host the site answers on.

  • •

    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

    5 schema types on the 3 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://taylortaxandfinancial.com/.

  • ✓

    Mixed content

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

  • ✓

    Sitemap

    Sitemap at https://taylortaxandfinancial.com/sitemap.xml — 2336 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://taylortaxandfinancial.com/.

  • ✓

    Language declared

    <html lang="en">.

  • ✓

    Redirect chain

    The URL answers directly, with no redirect.

  • ✓

    robots.txt

    robots.txt is served (1 group, 1 sitemap line).

  • ✓

    Sitemap named in robots.txt

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

  • ✓

    www and apex agree

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

  • ✓

    Lighthouse SEO score

    Lighthouse SEO 100/100.

  • ✓

    Sitemap dates

    2336 pages with lastmod dates, from 2022-02-23 to 2026-11-09.

On-page SEO & content 8 of 25 points

  • ✗

    Page title

    “IRS Wage Levy and Bank Levy Help | Taylor Tax & Financial | Taylor Tax & Financial Consult…” is 97 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.

  • ✗

    Titles across the site

    the service page's title is 62 characters; the post page's title is 75 characters.

    What we’d do: Every page gets its own 30–60 character title, checked in the build.

  • ✗

    Pages that repeat each other

    13 of the 13 sentences on the post page also appear on the home page (100%). Pages that repeat each other with a word swapped are what Google's scaled-content rules are written against.

    What we’d do: Every page is written once, for its own subject, from the business's own facts — no page is another with the city swapped.

  • ✗

    Canonical and share card on every page

    The service page (/services/new-business-formation) has no share image and no H1; the post page (/preview/site/taylor-tax-financial-consulting-inc-686d3a6a916ff/blog) has a canonical naming /blog, another page, no share image and no H1.

    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.

  • ✗

    Service pages link each other

    The service page read links none of the other 11 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.

  • ✗

    Article schema on the post

    The post https://taylortaxandfinancial.com/blog/blog-content has no Article or BlogPosting schema — no author, no date, nothing for the engines to cite.

    What we’d do: Every post carries BlogPosting schema with its author, dates and publisher.

  • !

    Social share cards

    Only part of the share markup: Twitter card is there, Open Graph is not.

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

  • !

    Single H1

    2 H1 headings. One is the convention search engines and screen readers expect.

    What we’d do: One H1 per page; the rest become H2s.

  • !

    Descriptions across the site

    the service page's description is 184 characters.

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

  • !

    No stock or AI-marked pictures

    1 picture marked as bought stock on the pages read: open-sign-GettyImages-1279654273-2500___media_library_original_2500_1663.jpg (a Getty Images download's name). Visitors comparing businesses, and Google's quality raters, look for photos of the business's own work.

    What we’d do: The owner's own photos of real jobs are the proof of work, in every section that shows the work; a stock or generated picture only ever sets the mood, and it is named and described for what it shows.

  • !

    A menu a thumb can use

    12 links in the header and menu.

    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 read

    Read with the home page: service page https://taylortaxandfinancial.com/services/new-business-formation; post page https://taylortaxandfinancial.com/blog/blog-content.

  • ✓

    Meta description

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

  • ✓

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

  • ✓

    No placeholder or template text

    No template or placeholder text on the 3 pages read — no lorem ipsum, sample address or number, “add your text here”, or “undefined” where a value should be.

  • ✓

    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 22 images have an alt attribute.

  • ✓

    Readable content in the HTML

    6,339 words of readable text in the HTML.

  • ✓

    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

    12 service pages in the sitemap (/services/new-business-formation, /services/strategic-business-planning, /accounting-bookkeeping-1, …).

  • ✓

    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 (/) and a privacy policy (/about-us/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.

  • ✗

    Questions answered on the page

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

    Neither inner page read carries a 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.

  • !

    Schema on the inner pages

    The service page (/services/new-business-formation) has no BreadcrumbList; the post page (/preview/site/taylor-tax-financial-consulting-inc-686d3a6a916ff/blog) has no BreadcrumbList.

    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.

  • !

    AI crawlers allowed

    robots.txt lets every answer engine in: GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User and the rest. The site answers GPTBot and ClaudeBot with 444 while a browser gets the page, so those engines may not be able to read it.

    What we’d do: The crawlers get the page a browser gets: we find the rule that answers them differently (the host's firewall, a security plugin) and open it to the answer engines.

  • !

    The first paragraph answers

    The service page has no H1 to answer under.

    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.

  • ✓

    Specifics an engine can cite

    The service page (/services/new-business-formation): 5,014 words, 115 numbers, 31 names (Identification, CountingWorks, France, Germany, …); the post page (/preview/site/taylor-tax-financial-consulting-inc-686d3a6a916ff/blog): 4,812 words, 130 numbers, 54 names (Filed, Unfiled, Returns, Actually, …) — specifics only this business could publish, the kind an answer engine quotes.

  • ✓

    Readable without JavaScript

    The page's 6,339 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

    3 schema types: LocalBusiness, AccountingService, PostalAddress.

  • ✓

    Extractable structure

    Structure an engine can lift: 20 H2s, 0 H3s, 27 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.

  • ✗

    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.

  • !

    Business schema completeness

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

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

  • !

    Linked to its profiles

    The page links Facebook and Instagram, but the business node has no sameAs naming them, so the engines have to guess that they are the same business.

    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.

  • !

    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.

  • •

    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

    LocalBusiness / AccountingService schema names the business.

  • ✓

    Address and phone on the page

    The phone ((615) 953-7124) and where the business is (301 S Perimeter Park Dr Suite) are on the page as text, and the phone matches the schema's.

  • ✓

    The trade's own schema type

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

  • ✓

    Trust signals

    Trust language present: guarantee, years of experience, enrolled agent, 19 years.

Speed, scripts & mobile 8 of 20 points

  • ✗

    Scripts and third parties

    12 scripts, 1276 KB of JavaScript, from 3 third parties (analytics.countingworkspro.com, www.google.com and reCAPTCHA). Google CDN 0.6 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.

  • ✗

    Image hygiene

    22 images: 0 with dimensions, 0 in a modern format or through an image service, 0 lazy-loaded. 22 of 22 images have no width and height, so the page jumps as they load; 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.

  • ✗

    Readable and tappable on a phone

    38 pieces of text are too faint to read against their background (“Schedule Appointment” 1.74:1, “tjtaylor@taylortaxandfinancial.com” 1.74:1, “If the IRS is threatening to garnish your wages, levy your bank account, or col…” 1.97:1); WCAG asks 4.5:1 for text that size. Google's test read the page as a phone shows it.

    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.

  • !

    Lighthouse accessibility score

    Lighthouse accessibility 75/100 — the report names what to fix.

    What we’d do: Contrast, labels, landmarks and focus order are checked on every page before it ships.

  • !

    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.

  • !

    Fonts

    5 font files (180 KB) from Google Fonts. 1 face 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.

  • !

    Page weight

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

  • !

    Static files cached

    15 files served with a short or missing cache lifetime, 8 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.

  • !

    What would speed it up most

    PageSpeed's biggest savings on this page: Render-blocking requests (about 0.8 s); Minimize main-thread work (about 0.5 s); Reduce JavaScript execution time (about 0.5 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 87/100. Google's own bands: 90 and up is good, 50–89 needs improvement.

  • ✓

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

  • ✓

    The hero image loads first

    The largest thing on the first screen is text or a styled block (<p class=" text-base text-left text-gray-500 font-body leading-6 mt-2 ), 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.

  • ✓

    Time to first byte

    First byte in 207 ms from our server.

  • ✓

    HTML weight

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

Conversion & lead generation 4 of 5 points

  • ✗

    No CAPTCHA puzzle

    reCAPTCHA v2 on the form: a puzzle the visitor has to solve, and several hundred KB of Google's scripts on every page that carries it.

    What we’d do: Turnstile, or a honeypot and a time trap, on the form: nothing the visitor has to solve, under 20 KB, and the lead stored before it is emailed.

  • !

    A lead form that fits a phone

    The lead form asks 5 fields and 2 checkboxes or radio buttons; 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

    1 form 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, guarded by reCAPTCHA.

  • ✓

    Analytics installed

    Measured by Plausible.

  • ✓

    Tappable phone number

    1 tel: link — the number dials from a phone.

Read with the home page: service page taylortaxandfinancial.com/services/new-business-formation · post page taylortaxandfinancial.com/blog/blog-content

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