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

builtforwardpartners.com scored 37/100 on the website scan.

Major issues

builtforwardpartners.com · Scanned 2026-10-27

45 passed17 warnings14 failed

  • Technical SEO & indexability6 of 10 points
  • On-page SEO & content8 of 25 points
  • AI search / AEO / GEO readiness10 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 +8 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 +8 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

    Only 1 question asked and answered on the pages read (1 on the home 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.

  • ✗

    Page title +4 points

    The home page has no <title>.

    What we’d do: Every page gets a title of 30–60 characters with the service, the place and the name.

  • ✗

    Meta description +4 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.

  • !

    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.

  • !

    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.

  • !

    robots.txt

    No robots.txt. Crawlers assume everything is allowed, and nothing points them at the sitemap.

    What we’d do: A robots.txt that names the sitemap and keeps only the private paths out.

  • !

    Lighthouse SEO score

    Lighthouse SEO 82/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.

  • •

    Sitemap named in robots.txt

    Skipped — no robots.txt.

  • •

    Sitemap lists the live URLs

    The sitemap lists no page URLs to check.

  • •

    Sitemap dates

    The sitemap carries no lastmod dates. Search engines then decide for themselves when to recrawl.

  • ✓

    Indexable by search engines

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

  • ✓

    Structured data Google accepts

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

  • ✓

    Mixed content

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

  • ✓

    Sitemap

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

  • ✓

    Internal links resolve

    All 5 internal links read on the home page answer.

  • ✓

    Language declared

    <html lang="en">.

  • ✓

    Redirect chain

    The URL answers directly, with no redirect.

  • ✓

    www and apex agree

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

  • ✓

    Lighthouse best practices

    Lighthouse best practices 100/100.

On-page SEO & content 8 of 25 points

  • ✗

    Page title

    The home page has no <title>.

    What we’d do: Every page gets a title of 30–60 characters with the service, the place and the name.

  • ✗

    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.

  • !

    Pictures named and described for what they show

    Of the 3 pictures on the pages read, 3 with a camera's, a template's or an upload's name (6acd3856412f76b5268eed22.png, 6acd3857011eef2fd1509994.jpeg, 6acd385604c496731f393716.png). Google's image guidelines ask for file names and alt text that say what the picture shows.

    What we’d do: Every picture is named for what it shows, in the business's own words (franklin-standing-seam-metal-roof.webp, never IMG_4411.jpg), and its alt text says what is in it — the job, the place, the material — rather than a keyword.

  • !

    A page for each service

    Only 2 service pages linked from the home page (no sitemap to read) (/audit-my-website, /ai-demo). 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.

  • •

    Titles across the site

    Skipped — no inner page read.

  • •

    Share image loads

    Skipped — no og:image to fetch.

  • •

    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.

  • •

    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.

  • ✓

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

  • ✓

    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: “More booked consults from the traffic you already get”.

  • ✓

    Image alt text

    All 3 images have an alt attribute.

  • ✓

    Readable content in the HTML

    1,391 words of readable text in the HTML.

  • ✓

    Favicon

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

  • ✓

    About and privacy pages

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

  • ✓

    A menu a thumb can use

    3 links in the header and menu.

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

    Only 1 question asked and answered on the pages read (1 on the home 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.

  • •

    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 1,391 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

    1 schema type: WebPage.

  • ✓

    Extractable structure

    Structure an engine can lift: 8 H2s, 23 H3s, 6 list items.

  • ✓

    AI crawlers allowed

    No robots.txt, so every AI crawler is allowed by default. 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 30 words on the home page.

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.

  • ✗

    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.

  • !

    Address and phone on the page

    The phone is on the page, but not the town or the street address. Map search and the answer engines place a business 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.

  • !

    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.

  • !

    Trust signals

    Only guarantee. 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 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.

Speed, scripts & mobile 11 of 20 points

  • ✗

    Image hygiene

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

  • ✗

    Largest Contentful Paint (LCP)

    Largest Contentful Paint 31.4 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

    5.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 65/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.

  • !

    Scripts and third parties

    24 scripts, 375 KB of JavaScript, from 2 third parties (GoHighLevel and static.cloudflareinsights.com). Every script is a download, a parse and a run on a phone before the visitor can tap anything.

    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.

  • !

    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.

  • !

    No fixed-width overflow

    1 inline width of 420px — likely to overflow a 375px phone screen.

    What we’d do: Widths are fluid (max-width, percentages, grid) so nothing is wider than the screen.

  • !

    What would speed it up most

    PageSpeed's biggest savings on this page: Improve image delivery (about 25.8 s); Render-blocking requests (about 0.9 s); Reduce unused JavaScript (about 0.8 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.

  • ✓

    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.

  • ✓

    Lighthouse accessibility score

    Lighthouse accessibility 96/100.

  • ✓

    Nothing blocks the first paint

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

  • ✓

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

  • ✓

    Fonts

    3 font files (90 KB) from Google Fonts.

  • ✓

    Pinch-to-zoom allowed

    Pinch-to-zoom is allowed.

  • ✓

    Time to first byte

    First byte in 315 ms from our server.

  • ✓

    HTML weight

    About 38 KB compressed (190 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

    One chat widget (GoHighLevel chat).

  • ✓

    Static files cached

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

Conversion & lead generation 2 of 5 points

  • ✗

    Contact form

    No form and no contact link on the home page.

    What we’d do: A short quote form on every page, stored first and emailed second.

  • !

    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.

Want this fixed?

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