No JSON-LD blocks found on any of the 1 pages checked.

Why it matters: JSON-LD is the one block on a page written purely for machines. Without it, an answer engine has to guess the business’s identity from prose — and it usually names a competitor it can read cleanly instead.

Next step: Add a JSON-LD block (LocalBusiness or Organization) to the site template so every page carries the business entity.

Source: the JSON-LD blocks in the pages read · Confidence: Direct read

No LocalBusiness or Organization type found in the schema on any checked page.

Why it matters: A specific type ("Plumber", "RoofingContractor") tells an engine exactly what the business is and which local questions it answers. A generic Organization label leaves the engine to infer the trade.

Next step: Add LocalBusiness-subtype schema (e.g. GeneralContractor) naming the business, its trade, and where it works.

Source: the business entity’s @type in the crawled JSON-LD · Confidence: Direct read

No business schema node found, so none of the 8 key fields (name, phone, street address, URL, sameAs, hours, geo, service area) are published.

Why it matters: Each field is a question an engine can then answer without guessing — the phone for "call", the street for "near me", hours for "open now". Missing fields are questions the engine answers with someone else’s data.

Next step: Publish a business schema node carrying name, phone, street address, URL, profile links, hours, geo, and service area.

Source: the most complete business entity found in the crawled JSON-LD · Confidence: Direct read

No FAQPage schema on any checked page.

Why it matters: FAQPage schema hands engines pre-formatted question-and-answer pairs they can lift word-for-word into an answer — the closest thing to writing the answer yourself.

Next step: Add FAQPage schema mirroring the visible FAQ questions and answers (the schema must match what visitors see).

Source: JSON-LD @type values across the pages read · Confidence: Direct read

No Service schema found — services are described only in page text.

Why it matters: Service schema names each service as a machine-readable fact, so "who replaces water heaters in Long Beach?" can match the business on a stated service instead of a keyword buried in a paragraph.

Next step: Add Service schema for each core service, tied to the business and its service area.

Source: JSON-LD @type values across the pages read · Confidence: Direct read

No AggregateRating or Review schema found on any checked page.

Why it matters: Marked-up ratings give engines a citable proof number. A rating that exists only on Google’s own pages never reaches the answers assembled from the open web.

Next step: Once real reviews are published on the site, mark them up with Review / AggregateRating schema that matches them exactly.

Source: JSON-LD @type values across the pages read · Confidence: Direct read

No robots.txt found (HTTP 404) — crawlers get no instructions at all.

Why it matters: robots.txt is the instruction sheet crawlers read first. Without one they get no guidance — no sitemap pointer, no explicit welcome — and some simply crawl less.

Next step: Publish a robots.txt that welcomes search and AI crawlers and points to the sitemap.

Source: /robots.txt · Confidence: Direct read

No rule blocks the major AI crawlers — GPTBot: allowed · PerplexityBot: allowed · ClaudeBot: allowed.

No valid sitemap found at /sitemap.xml, /sitemap_index.xml, or /wp-sitemap.xml.

Why it matters: The sitemap is the map handed to crawlers. Pages missing from it are found late, by accident, or not at all — including the service pages that carry local questions.

Next step: Publish a sitemap.xml (or sitemap index) listing every public page, and reference it in robots.txt.

Source: the sitemap file listed in the appendix · Confidence: Direct read

No llms.txt found (HTTP 404).

Why it matters: llms.txt is the short, plain-text brief written for AI tools: who the business is, what it does, and which pages matter. It is the cheapest signal on this list to publish.

Next step: Publish an llms.txt at the site root: what the business does, where it works, and links to the key pages.

Source: /llms.txt · Confidence: Direct read

No llms.txt to evaluate.

Why it matters: A stub llms.txt tells an AI tool almost nothing. One that links the money pages — services, cities, guides — steers the tool to the pages worth citing.

Next step: Give llms.txt real substance — a business summary plus links to services, cities, contact, and FAQ pages.

Source: the body of /llms.txt · Confidence: Direct read

Homepage has no canonical tag; site serves clean HTTPS.

Why it matters: A canonical tag tells engines which URL is the real one, so citations and ranking signals land on one page instead of splitting across duplicates. HTTPS is table stakes for being treated as a trustworthy source.

Next step: Add a self-referencing canonical tag to every page and serve the whole site over HTTPS.

Source: the homepage <head> (canonical link) and the site’s URL scheme · Confidence: Direct read

0 question-and-answer blocks found across the checked pages (0 question-style headings; no dedicated FAQ page found).

Why it matters: Homeowners ask engines whole questions. Pages that state those questions and answer them in plain text give the engine something it can lift verbatim — that is what gets cited.

Next step: Publish Q&A content: the questions customers ask, answered in plain words on an FAQ page and service pages.

Source: question-style headings and FAQ blocks across the pages read · Confidence: Limited — the crawl covered only 1 page, so this rests on a thin read of the site

0 service+city / city pages found (0 combined service+city, 0 dedicated city pages); 0 service pages without a city in the address.

Why it matters: Local questions need a local page to land on: "Roof Replacement in Long Beach" has to exist as a page before an engine can cite it. One generic services page answers every city weakly and none of them well.

Next step: Create dedicated pages for the core services in the core cities served (e.g. "Roof Replacement in Long Beach").

Source: the page addresses collected from the sitemap and internal links · Confidence: Limited — inferred from page addresses collected during the crawl — the audit did not open every page on the site

Homepage runs 672 words; the main services page runs 0 words. Thin pages give engines little to cite.

Why it matters: Thin pages give an engine almost nothing to work with. A homepage and services page with real substance — services, areas, process, prices where published — are what answers get built from.

Next step: Deepen the homepage and services page: what you do, where, for whom, with specifics an engine can quote.

Source: the visible text of the homepage and the services page · Confidence: Limited — the crawl covered only 1 page, so this rests on a thin read of the site

Homepage has 1 H1 heading and 5 descriptive H2 sections.

0 of 1 checked pages carry a clean page title and a meta description in a sane length.

Why it matters: The title is the one-line summary engines and search results quote; the meta description is the supporting sentence. Missing or bloated ones cost the click and weaken the citation.

Next step: Give every key page a unique title and a one-sentence meta description naming the service and the place.

Source: the <title> and meta description of each page read · Confidence: Limited — the crawl covered only 1 page, so this rests on a thin read of the site

6 short factual blocks (tight paragraphs and lists) found on the homepage/services page — the shapes engines lift answers from.

Phone (714) 865-5731 is printed on the site but missing from the schema. No business name in schema to compare against the pages. No street address found in the schema or the pages checked.

Why it matters: Engines match a business to "near me" by reconciling its name, address, and phone everywhere they appear. When the schema, the homepage, and the contact page disagree, the match weakens — or the engine prints the wrong number.

Next step: Publish ONE name, phone, and street address (or explicit service area) — identical in the schema, footer, and contact page.

Source: compared across the schema, the homepage text, and the contact page · Confidence: Limited — the crawl covered only 1 page, so this rests on a thin read of the site

tel: click-to-call links found — a phone tap on mobile reaches the business directly.

No contact page found among the site links or sitemap.

Why it matters: A dedicated contact page is the page engines point people to. If it is missing or bare, the citation has nowhere useful to land.

Next step: Publish a dedicated contact page with the NAP, a form, and a click-to-call number.

Source: the contact page found in the crawl, or its absence from it · Confidence: Limited — the crawl covered only 1 page, so this rests on a thin read of the site

No links to review profiles (Google, Yelp, Houzz, BBB…) found on the checked pages.

Why it matters: Links to Google, Yelp, and the trade directories connect the site to its proof. Engines cite businesses they can corroborate — an unlinked profile is corroboration they may never find.

Next step: Link the Google and Yelp review profiles from the footer and contact page so engines can cite real proof.

Source: outbound links in the pages read · Confidence: Limited — the crawl covered only 1 page, so this rests on a thin read of the site

No testimonials found on the checked pages.

Why it matters: Visible testimonials are proof in the site’s own words that an engine can quote. A star number buried in code is not proof; a named customer sentence is.

Next step: Publish real customer testimonials (name, city, job type) on the homepage and service pages.

Source: testimonial-style content in the pages read · Confidence: Limited — detected by content patterns in the pages read, not by a registry — a page the crawl did not reach could hold more

No Google Business Profile or Maps profile link found on the checked pages.

Why it matters: A published link to the Google Business Profile ties the website to the listing that powers maps and "near me" answers, closing the loop engines use to confirm the business is real and current.

Next step: Link the Google Business Profile from the footer and contact page.

Source: outbound links in the pages read · Confidence: Limited — the crawl covered only 1 page, so this rests on a thin read of the site