News from Google | Google Product and Technology News and Stories

No active Strict-Transport-Security max-age was observed.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.

Add HSTS (e.g. max-age=63072000; includeSubDomains) so browsers never even try HTTP after the first visit.

No frame-embedding restriction was observed (neither CSP frame-ancestors nor X-Frame-Options).

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.

Send Content-Security-Policy: frame-ancestors 'self' (or 'none', or a list of partner origins), or X-Frame-Options: SAMEORIGIN. It stops other sites from framing your pages to trick visitors into clicking (clickjacking).

X-Content-Type-Options: nosniff is not set.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.

Add it — one header, stops MIME-sniffing attacks. Most hosts let you set headers in config (vercel.json, netlify.toml, next.config).

No explicit restriction on sensitive browser features was observed.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. It is there, but weaker than this check expects.

Disable unused camera, microphone, or geolocation access using Permissions-Policy.

No HTML forms were found.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.

Check JavaScript-generated form transport separately if present.

No enabled, named password inputs in sampled HTML.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. This check does not apply to the features observed in this sample.

Review authentication forms separately when applicable.

Site serves over HTTPS.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Nothing to do here.

http:// permanently redirects to https://./

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Nothing to do here.

An enforced CSP restricts scripts and object embedding.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Review the complete policy against the application's resource and inline-script needs.

No Referrer-Policy is set, so browsers apply their default, strict-origin-when-cross-origin, which sends only the origin to other sites.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Nothing to do here.

No insecure subresources detected.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Nothing to do here.

No X-Powered-By disclosure.

HTTPS protects what visitors send you, and response headers limit what a hostile page can do in their browser. The inspected source provides this signal.

Nothing to do here.

Entity identity is inconsistent: the declared names differ (og:site_name "blog.google", WebSite name "News from Google").

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

Use one name for the site everywhere it is declared (Organization/WebSite schema, og:site_name, the title) and point identity URLs at this site.

• https://blog.google/

No /llms.txt file.

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

Optional: publish an llms.txt index of useful pages. This proposal is not a requirement for Google AI features, and its absence does not reduce the core score.

No FAQPage or QAPage schema on any crawled page.

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

If the page answers recurring questions, use visible question-and-answer content and matching FAQPage markup. QAPage is for a single question with user-submitted answers. Google FAQ rich results are restricted to eligible authoritative government and health sites; markup does not guarantee AI citations.

Only 6% of 70 H2/H3 headings are question-shaped.

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

Phrase key subheadings as the questions users actually ask ("How much does X cost?"). This improves the measured question-heading signal; the audit does not guarantee citations.

The opening paragraph doesn't define what the site/topic is: "Learn more:…"

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

"X is a Y that does Z for W" in the first paragraph gives answer engines a liftable definition of you. Write it once, benefit everywhere.

1/4 question-shaped heading(s) have a 20–500 character paragraph immediately after them.

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

Put a direct 20–500 character answer paragraph immediately after each question heading so retrieval systems can quote it cleanly.

• https://blog.google/

Only 3 of 4 provenance signal types were found: author, contact, breadcrumb.

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

Add the missing author, date, breadcrumb, or contact signal so machines can identify provenance and site structure.

• https://blog.google/
• https://blog.google/about/
• https://blog.google/innovation-and-ai/models-and-research/google-deepmind/
• https://blog.google/products-and-platforms/products/search/
• https://blog.google/company-news/outreach-and-initiatives/creating-opportunity/
• https://blog.google/authors/sundar-pichai/

No markdown copy answered at /index.md or /about/index.md or /index.html.md.

This is what an AI assistant relies on when deciding whether it can quote your page. It is there, but weaker than this check expects.

Publish a clean markdown copy of each key page at /page.md (or /page.html.md). It strips navigation and scripts, so a retriever spends its budget on your content.

• https://blog.google/
• https://blog.google/about/

No /llms-full.txt.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Optional companion to llms.txt containing your full content as one markdown file — useful for sites whose pages are JS-heavy.

No Article/BlogPosting schema found.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add Article schema with author and datePublished so the page exposes clear provenance for retrieval. This audit does not measure or guarantee citations or rankings.

26 concrete figures across 1531 words.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Good — keep facts specific and current, and date-stamp them.

No readable llms.txt was available to inspect for Markdown links.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Publish a readable llms.txt, then link its important pages with same-origin Markdown URLs.

No readable /llms.txt, so its structure cannot be checked.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Publish llms.txt first — the llms.txt check covers that — then this one verifies the structure.

The homepage answered Accept: text/markdown with text/html; charset=utf-8.

This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.

Optional: return a stripped markdown body when the request asks for text/markdown. Some hosts and CDNs do this for you; a plain HTML answer is not a defect.

No OpenAPI interface was advertised by sampled HTML.

This is what an AI assistant relies on when deciding whether it can quote your page. This check does not apply to the features observed in this sample.

An API is optional. Add a service-desc link if you already publish a machine-readable API specification.

The audited URL is allowed for evaluated answer-search crawlers.

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Nothing to do here.

Semantic structure present: main×1, article×10, section×21, nav×2, header×2, footer×1.

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Nothing to do here.

Paragraphs get to the point without preamble.

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Nothing to do here.

Paragraphs average 9 words, lists present — chunk-friendly.

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Nothing to do here.

dateModified present in schema.

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Nothing to do here.

101 outbound reference(s) across crawled pages.

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Nothing to do here.

Brand declared: og:site_name "blog.google" + identity schema.

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Nothing to do here.

Meta description works as a standalone summary.

This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.

Nothing to do here.

No privacy policy page is linked or crawlable.

A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.

Publish an accessible privacy policy that discloses cookies and data use by Google and other third-party ad vendors.

7/9 editorial pages expose fewer than 80 publisher words in source HTML. 1 of the 10 sampled pages is a support or tool page and was excluded from this check.

A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.

Add crawlable explanation or original publisher material to those pages. Most of the sample currently reads as chrome rather than content.

• https://blog.google/feed/
• https://blog.google/innovation-and-ai/models-and-research/google-deepmind/
• https://blog.google/products-and-platforms/products/search/
• https://blog.google/products/ads-commerce/
• https://blog.google/waze/
• https://blog.google/company-news/outreach-and-initiatives/creating-opportunity/
• https://blog.google/security/

No terms of use page found.

A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.

Consider adding terms that identify the service rules and publisher. This is a transparency heuristic, not an AdSense requirement.

No contact page or mailto link found.

A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.

Add a working contact route or visible email so users can reach the publisher. This is a trust heuristic, not a published approval rule.

7/9 editorial pages expose fewer than 80 publisher words. 1 of the 10 sampled pages is a support or tool page and was excluded from this check.

A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.

Review these pages for a clear purpose and useful publisher material. This cutoff is a triage heuristic, not an AdSense minimum.

• https://blog.google/feed/ (12 publisher words)
• https://blog.google/innovation-and-ai/models-and-research/google-deepmind/ (15 publisher words)
• https://blog.google/products-and-platforms/products/search/ (5 publisher words)
• https://blog.google/products/ads-commerce/ (14 publisher words)
• https://blog.google/waze/ (6 publisher words)
• https://blog.google/company-news/outreach-and-initiatives/creating-opportunity/ (14 publisher words)
• https://blog.google/security/ (3 publisher words)

7/10 tool-style screen(s) expose fewer than 80 publisher words. Google publishes no minimum word count; this is an audit heuristic.

A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.

Explain the tool's purpose, inputs, method, limitations, and result interpretation in source HTML. Add useful material, not filler.

• https://blog.google/feed/
• https://blog.google/innovation-and-ai/models-and-research/google-deepmind/
• https://blog.google/products-and-platforms/products/search/
• https://blog.google/products/ads-commerce/
• https://blog.google/waze/
• https://blog.google/company-news/outreach-and-initiatives/creating-opportunity/
• https://blog.google/security/

8/10 crawled pages don't link to the privacy policy.

A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.

Place the privacy link in shared navigation or footer markup so users can reach disclosures from any sampled entry page.

• https://blog.google/feed/
• https://blog.google/innovation-and-ai/models-and-research/google-deepmind/
• https://blog.google/products-and-platforms/products/search/
• https://blog.google/products/ads-commerce/
• https://blog.google/waze/
• https://blog.google/company-news/outreach-and-initiatives/creating-opportunity/
• https://blog.google/authors/sundar-pichai/
• https://blog.google/security/

Contact email does not align with blog.google: press@google.com.

A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.

Use an address on the publisher's domain when practical so readers can verify the publisher identity. This is a practitioner trust heuristic, not an AdSense requirement.

6/8 sampled editorial pages lack detectable author attribution.

A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.

Identify who created editorial content with a visible byline, author link, or matching Article author markup. This is a transparency heuristic, not an AdSense approval rule.

• https://blog.google/innovation-and-ai/models-and-research/google-deepmind/
• https://blog.google/products-and-platforms/products/search/
• https://blog.google/products/ads-commerce/
• https://blog.google/waze/
• https://blog.google/company-news/outreach-and-initiatives/creating-opportunity/
• https://blog.google/security/

A privacy page was not present in the crawl sample, so its disclosures could not be verified.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Confirm the policy explains cookies or similar storage, Google or advertising vendors, and third-party data use.

No ads.txt yet.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

When AdSense provides your publisher entry, publish it exactly at /ads.txt and monitor authorization status in your account.

No cookie-consent banner or CMP script detected.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Before serving Google ads in the EEA, UK, or Switzerland, implement a Google-certified consent management platform that integrates with the IAB TCF.