wiseowloutfitters.com scored 42/100 on the website scan.
Needs work
wiseowloutfitters.com · Scanned 2026-11-13
59 passed16 warnings17 failed
- Technical SEO & indexability8/10 of 10 points
- On-page SEO & content9/25 of 25 points
- AI search / AEO / GEO readiness11/35 of 35 points
- Local SEO & entity signals1/5 of 5 points
- Speed, scripts & mobile10/20 of 20 points
- Conversion & lead generation3/5 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 +5 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 +5 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 +5 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.
-
✗
Schema on the inner pages +3 points
The service page (/agents.md) 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.
-
✗
Titles across the site +3 points
the service page has no title.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
Every check, by category (103 checks)
Technical SEO & indexability 8 of 10 points
-
✗
Internal links resolve
2 of the 36 internal links read (30 on the home page, 6 in llms.txt) lead nowhere: /customer_authentication/redirect?locale=en®ion_country=US (too many redirects), /api/ucp/mcp (404, in llms.txt). A visitor who taps one gets an error page, and a crawler that follows it finds nothing to index.
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.
-
!
Security headers
Missing: Referrer-Policy.
What we’d do: Content-Security-Policy, X-Content-Type-Options, frame protection and Referrer-Policy on every response.
-
•
HTTPS certificate
The certificate could not be read from this platform, but the page was fetched over HTTPS.
-
•
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
3 schema types 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.
-
✓
Canonical URL
Canonical is https://wiseowloutfitters.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.
-
✓
Sitemap
Sitemap at https://wiseowloutfitters.com/sitemap.xml — an index of 6 sitemaps.
-
✓
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://wiseowloutfitters.com/.
-
✓
Language declared
<html lang="en">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
robots.txt
robots.txt is served (2 groups, 1 sitemap line).
-
✓
Sitemap named in robots.txt
robots.txt names the sitemap: https://wiseowloutfitters.com/sitemap.xml.
-
✓
www and apex agree
www.wiseowloutfitters.com redirects (301) to wiseowloutfitters.com.
-
✓
Sitemap lists the live URLs
The sitemap's 1 URL is on https://wiseowloutfitters.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 9 of 25 points
-
✗
Titles across the site
the service page has no title.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
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.
-
✗
Canonical and share card on every page
The service page (/agents.md) has no canonical, no share image, no Twitter card 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.
-
!
Page title
“Camping Hammocks, Outdoor Gear, Accessories | Wise Owl Outfitters” is 65 characters. Google shows about 60 and cuts the rest, so the end of it is lost in results.
What we’d do: We write titles of 30–60 characters, the topic first and the brand last, so nothing is cut.
-
!
Meta description
162 characters. Google shows about 160 and cuts the rest with an ellipsis.
What we’d do: We write descriptions of 120–160 characters, the point first.
-
!
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.
-
!
A page for each service
Only 1 service page in the sitemap (/agents.md). 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.
-
!
A menu a thumb can use
The service page read (/agents.md) 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.
-
•
Service pages link each other
Skipped — fewer than three service pages to link between.
-
•
Pages read
Read with the home page: service page https://wiseowloutfitters.com/agents.md.
-
•
Article schema on the post
No post found in the sitemap to check.
-
✓
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 79 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: “”.
-
✓
Image alt text
All 95 images have an alt attribute.
-
✓
Readable content in the HTML
439 words of readable text in the HTML.
-
✓
Pages that repeat each other
The pages read share no sentences beyond the header, footer and calls to action.
-
✓
Pictures named and described for what they show
59 of the 62 pictures on the pages read are named and described for what they show (not: 3 with alt text that describes nothing (“Hammock Sleeve” on 3 pictures)).
-
✓
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 (/pages/about) and a privacy policy (/policies/privacy-policy).
-
✓
Titles lead with the subject
The inner pages' titles lead with their subject, not the business name.
AI search / AEO / GEO readiness 11 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.
-
✗
Schema on the inner pages
The service page (/agents.md) 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.
-
✗
The first paragraph answers
The home page's headline is followed by buttons and pictures, not a sentence; the service page has no H1 to answer under. An answer engine quotes the sentence right under the heading.
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.
-
✓
llms.txt
llms.txt is published (6 KB), headed with the name and linking 7 pages of the site — a plain statement of the business for the AI engines to read.
-
✓
Specifics an engine can cite
The service page (/agents.md): 796 words, 4 numbers, 20 names (UCP, WebMCP, Pay, Universal, …) — specifics only this business could publish, the kind an answer engine quotes.
-
✓
Readable without JavaScript
The page's 439 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: Organization, WebSite, SearchAction.
-
✓
Extractable structure
Structure an engine can lift: 7 H2s, 0 H3s, 43 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.
Local SEO & entity signals 1 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.
-
✗
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.
-
✗
The trade's own schema type
Organization only: it says a company exists, not what it does or where.
What we’d do: The business node uses schema.org's own type for the trade — RoofingContractor, Plumber, HVACBusiness, Electrician, HousePainter, GeneralContractor, MovingCompany, Locksmith and the rest under HomeAndConstructionBusiness and LocalBusiness — so the engines file it under what it does, not only that it exists.
-
✗
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.
-
✗
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, logo or image but not telephone, address.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.
-
!
Linked to its profiles
sameAs names only Instagram. The Google Business Profile is the one the map pack and Google's AI read first.
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
Reviews are quoted but there is no rating or count beside them, and nothing says how many there are.
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.
-
•
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
Organization schema names the business.
-
✓
Site name for Google
WebSite schema names the site “Wise Owl Outfitters” — the name Google shows above each result.
Speed, scripts & mobile 10 of 20 points
-
✗
No popup on arrival
A Klaviyo form is loaded on the home page. A popup over a phone screen is the first thing a visitor has to get rid of, and Google's mobile guidelines count an intrusive interstitial against the page.
What we’d do: Nothing covers the page: no popup, no email gate, no spinning offer. The quote form sits in the page where the visitor is, and the only thing that moves is what they tap.
-
✗
Page weight
3.5 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 69/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
64 scripts, 444 KB of JavaScript, from 5 third parties (shop.app, cdn.shopify.com, Klaviyo and cdn-static.okendo.io). 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.
-
!
Nothing blocks the first paint
3 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.
-
!
Image hygiene
95 images: 95 with dimensions, 0 in a modern format or through an image service, 89 lazy-loaded. 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.
-
!
Fonts
4 font files (122 KB) from wiseowloutfitters.com and 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.
-
!
HTML weight
About 66 KB compressed (348 KB of HTML) — heavy for one page; the usual cause is inlined scripts and styles.
What we’d do: Our pages are 20–50 KB compressed: the words and the markup, nothing bundled in.
-
✓
Mobile viewport
The viewport meta tag is set for phones.
-
✓
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 100/100.
-
✓
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 (real visitors to the site, 28 days). Google's thresholds: 0.1 good, 0.25 poor.
-
✓
Interaction to Next Paint (INP)
Interaction to Next Paint 135 ms (real visitors to the site, 28 days). Google's thresholds: 200 ms good, 500 ms poor.
-
✓
The hero image loads first
The hero image is asked for early and not lazy-loaded (<img src="https://wiseowloutfitters.com/cdn/shop/files/WOO_Camo_HERO_0).
-
✓
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 433 ms from our server.
-
✓
Compression
Responses are compressed (br).
-
✓
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.2 s (real visitors to the site, 28 days). Google's thresholds: 2.5 s good, 4 s poor.
-
✓
Static files cached
5 files served with a short or missing cache lifetime, 1 of them the site's own.
-
✓
What would speed it up most
Nothing large left to fix. PageSpeed's remaining suggestions: Render-blocking requests (about 0.3 s); Improve image delivery (about 0.2 s); Legacy JavaScript (about 0.1 s).
Conversion & lead generation 3 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.
-
!
No CAPTCHA puzzle
hCaptcha on the page: no puzzle most of the time, but several hundred KB of script on every page load and a share of real visitors challenged.
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.
-
•
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
2 forms 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 /localization, guarded by reCAPTCHA and hCaptcha.
-
✓
Analytics installed
Measured by Google Analytics.
-
✓
A lead form that fits a phone
The lead form asks 1 field, labeled, and fits a phone screen.
Read with the home page: service page wiseowloutfitters.com/agents.md
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.
We can fix every issue on wiseowloutfitters.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.