www.yahoo.com scored 37/100 on the website scan.
Major issues
yahoo.com · Scanned 2026-10-31
55 passed14 warnings22 failed
- Technical SEO & indexability9/10 of 10 points
- On-page SEO & content7/25 of 25 points
- AI search / AEO / GEO readiness8/35 of 35 points
- Local SEO & entity signals2/5 of 5 points
- Speed, scripts & mobile9/20 of 20 points
- Conversion & lead generation2/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
-
✗
AI crawlers allowed +2 points
robots.txt blocks GPTBot (ChatGPT (training and search)), ChatGPT-User (ChatGPT, when a user asks about a page), ClaudeBot (Claude), PerplexityBot (Perplexity), Google-Extended (Gemini and Google's AI). Those engines cannot read the site, so they cannot recommend it. The host refuses OAI-SearchBot at the edge (429, while a browser gets the page): the engine can't read the site even though robots.txt allows it.
What we’d do: robots.txt lets the answer engines in — GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, Bingbot, Applebot — and keeps only the private paths out. The host's firewall and bot rules let in every crawler robots.txt allows, GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot among them.
-
✗
Page title +2 points
“Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos” is 71 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 +2 points
the post page's title is 79 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
Contact form +2 points
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.
-
✗
Scripts and third parties +2 points
108 scripts, 3204 KB of JavaScript, from 12 third parties (consent.cmp.oath.com, s.yimg.com, Google Ads and cdn.taboola.com and more). Google/Doubleclick Ads 0.6 s and Google Tag Manager 0.3 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.
Every check, by category (103 checks)
Technical SEO & indexability 9 of 10 points
-
!
robots.txt
robots.txt is served, but Claude-SearchBot and OAI-SearchBot have groups of their own that don't repeat the * group's Disallow: /info/p.gif, Disallow: /p/ and Disallow: /r/ and the rest. A crawler named in its own group follows only that group, so they may read what the site keeps from every other crawler.
What we’d do: Every group in robots.txt repeats the private paths, so a crawler named on its own is kept out of them too.
-
!
Sitemap named in robots.txt
robots.txt has no Sitemap: line — Google and Bing have to find the sitemap some other way.
What we’d do: Every robots.txt names the sitemap.
-
•
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
7 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://www.yahoo.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://www.yahoo.com/sitemap-index.xml — an index of 1035 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://www.yahoo.com/.
-
✓
Internal links resolve
All 30 internal links read on the home page answer.
-
✓
Language declared
<html lang="en-US">.
-
✓
Redirect chain
The URL answers directly, with no redirect.
-
✓
www and apex agree
yahoo.com redirects (301) to www.yahoo.com.
-
✓
Sitemap lists the live URLs
The sitemap's 4258 URLs are all on https://www.yahoo.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 96/100.
On-page SEO & content 7 of 25 points
-
✗
Page title
“Yahoo | Mail, Weather, Search, Politics, News, Finance, Sports & Videos” is 71 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 post page's title is 79 characters.
What we’d do: Every page gets its own 30–60 character title, checked in the build.
-
✗
Single H1
No H1 heading on the page — the one line that says what the page is about.
What we’d do: Every page gets one H1 that names the service and the place.
-
✗
Descriptions across the site
the post page's description is 97 characters.
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 post page (/news/politics/articles/trump-explodes-reporter-asked-canceled-134005608.html) has a canonical naming /politics/2026/10/trump-explodes-at-reporter-who-asked-about-canceled-rally-you-look-like-hell.html, another page.
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.
-
✗
A page for each service
No service pages in the sitemap: the site is one page, or its services share one. Each search is for one service, and a page that covers them all ranks for none.
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.
-
!
Social share cards
Only part of the share markup: Open Graph is there, the Twitter card is not.
What we’d do: Every page carries og:title, og:image, twitter:card and twitter:image.
-
!
Pictures named and described for what they show
Of the 84 pictures on the pages read, 84 with a camera's, a template's or an upload's name (https://media.zenfs.com/en/entertainment_weekly_785/33caaacf32aa4fb3e9e1ed731ba3912c.jpg, https://media.zenfs.com/en/people_218/0a2dea22d84e3cf0dfbf235bc36487cd.jpg, https://media.zenfs.com/en/reuters.com/9779cec2e5bcd7479a5e53d40776aa2a.jpg, …). 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.
-
!
About and privacy pages
The home page links a privacy policy but no About page. Google's quality raters are told to find out who is behind a site; an About page with the owner's name, the crew and the years is where a business answers that.
What we’d do: An About page with the owner and the crew by name, their photos and roles, and a privacy policy, both linked from every page's footer.
-
!
No stock or AI-marked pictures
1 picture marked as bought stock on the pages read: https://d29szjachogqwa.cloudfront.net/images/user-uploaded/xgettyimages-2264127831.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.
-
•
Title and H1 differ
Skipped — no title or no H1 to compare.
-
•
Service pages link each other
Skipped — no service page read.
-
•
Pages read
Read with the home page: post page https://www.yahoo.com/news/politics/articles/trump-explodes-reporter-asked-canceled-134005608.html.
-
✓
Meta description
127 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 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.
-
✓
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 185 images have an alt attribute.
-
✓
Readable content in the HTML
1,795 words of readable text in the HTML.
-
✓
Share image loads
The share image loads (image/png, 2 KB).
-
✓
Pages that repeat each other
The pages read share few sentences: at most 3 of 62 (5%) between the post and home pages.
-
✓
Favicon
A favicon is linked — it shows in the tab and beside the site in Google's results.
-
✓
Titles lead with the subject
The inner pages' titles lead with their subject, not the business name.
-
✓
A menu a thumb can use
1 link in the header and menu.
-
✓
Article schema on the post
NewsArticle schema with an author on the post.
AI search / AEO / GEO readiness 8 of 35 points
-
✗
AI crawlers allowed
robots.txt blocks GPTBot (ChatGPT (training and search)), ChatGPT-User (ChatGPT, when a user asks about a page), ClaudeBot (Claude), PerplexityBot (Perplexity), Google-Extended (Gemini and Google's AI). Those engines cannot read the site, so they cannot recommend it. The host refuses OAI-SearchBot at the edge (429, while a browser gets the page): the engine can't read the site even though robots.txt allows it.
What we’d do: robots.txt lets the answer engines in — GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, Bingbot, Applebot — and keeps only the private paths out. The host's firewall and bot rules let in every crawler robots.txt allows, GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot among them.
-
✗
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.
-
✗
FAQs on the inner pages
The post 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.
-
✗
The first paragraph answers
The home 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.
-
!
FAQPage schema
The page asks and answers 3 questions but carries no FAQPage schema, so the engines have to find them on their own.
What we’d do: The FAQ's questions and answers go into FAQPage schema, built from the same text so the two always match.
-
!
Questions answered on the page
Only 3 questions asked and answered on the pages read (3 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.
-
!
Schema on the inner pages
The post page (/news/politics/articles/trump-explodes-reporter-asked-canceled-134005608.html) 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.
-
•
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 post page (/news/politics/articles/trump-explodes-reporter-asked-canceled-134005608.html): 1,298 words, 26 numbers, 107 names (Google, Donald, Trump, Republican, …) — specifics only this business could publish, the kind an answer engine quotes.
-
✓
Readable without JavaScript
The page's 1,795 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
4 schema types: WebSite, NewsMediaOrganization, ImageObject, Organization.
-
✓
Extractable structure
Structure an engine can lift: 4 H2s, 77 H3s, 294 list items, 4 question headings.
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.
-
✗
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.
-
✗
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, logo or image but not telephone, address, areaServed, openingHours.
What we’d do: The business node carries every fact the profile shows: phone, address, hours, area served and logo.
-
!
Trust signals
Only 57 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.
-
•
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
NewsMediaOrganization schema names the business.
-
✓
Linked to its profiles
The business node's sameAs names Wikipedia/Wikidata, Instagram, TikTok, Facebook, LinkedIn, X and YouTube — the links the engines use to know this site and those profiles are one business.
-
✓
Site name for Google
WebSite schema names the site “Yahoo!”, also known as “Yahoo” and “Yahoo! News” — the name Google shows above each result.
-
✓
The trade's own schema type
NewsMediaOrganization: schema.org's own type for what the business does.
Speed, scripts & mobile 9 of 20 points
-
✗
Scripts and third parties
108 scripts, 3204 KB of JavaScript, from 12 third parties (consent.cmp.oath.com, s.yimg.com, Google Ads and cdn.taboola.com and more). Google/Doubleclick Ads 0.6 s and Google Tag Manager 0.3 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.
-
✗
Nothing blocks the first paint
10 files load before anything is drawn — styles and scripts in the head — and PageSpeed puts 1.2 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.
-
✗
Readable and tappable on a phone
10 pieces of text are too faint to read against their background (“News” 4.18:1, “Black Friday isn't here yet, but Amazon and Walmart just dropped major deals” 4.18:1, “Cabincore style is back, but there's a trick to looking chic instead of lumberj…” 4.18:1); WCAG asks 4.5:1 for text that size. 2 buttons or links are too small or too close to others to tap reliably (“CA Privacy Notice”, “Help”). 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.
-
✗
No fixed-width overflow
4 inline widths of 400px or more — the usual cause of sideways scrolling on a phone.
What we’d do: Widths are fluid (max-width, percentages, grid) so nothing is wider than the screen.
-
✗
HTML weight
About 241 KB compressed (1161 KB of HTML) — every visit downloads this before anything is drawn.
What we’d do: Our pages are 20–50 KB compressed: the words and the markup, nothing bundled in.
-
✗
Page weight
4.7 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 45/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.
-
!
Image hygiene
185 images: 185 with dimensions, 0 in a modern format or through an image service, 178 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.
-
!
What would speed it up most
PageSpeed's biggest savings on this page: Reduce JavaScript execution time (about 1.8 s); Minimize main-thread work (about 1.7 s); Render-blocking requests (about 1.2 s).
What we’d do: These are the first three things we would fix.
-
✓
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.
-
✓
Lighthouse accessibility score
Lighthouse accessibility 93/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.04 (real visitors to this page, 28 days). Google's thresholds: 0.1 good, 0.25 poor.
-
✓
Interaction to Next Paint (INP)
Interaction to Next Paint 183 ms (real visitors to this page, 28 days). Google's thresholds: 200 ms good, 500 ms poor.
-
✓
Fonts
2 font files (76 KB) from www.yahoo.com.
-
✓
The hero image loads first
The hero image is asked for early and not lazy-loaded (<img alt="" fetchpriority="high" width="720" height="480" decoding="as).
-
✓
Pinch-to-zoom allowed
Pinch-to-zoom is allowed.
-
✓
Time to first byte
First byte in 171 ms from our server.
-
✓
Compression
Responses are compressed (gzip).
-
✓
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.1 s (real visitors to this page, 28 days). Google's thresholds: 2.5 s good, 4 s poor.
-
✓
Static files cached
25 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.
-
✗
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.
-
•
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.
-
✓
No CAPTCHA puzzle
No CAPTCHA puzzle on the page.
Read with the home page: post page www.yahoo.com/news/politics/articles/trump-explodes-reporter-asked-canceled-134005608.html
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 www.yahoo.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.