Website report
Visit sitehttps://github.blog/
Updates, ideas, and inspiration from GitHub to help developers build and design software.
Audit Full discovery audit·Language American English (en-US)·Response HTTP 200·Served by Nginx
Analysed Nov 9, 2026 · 15 categories · 104 passed · 20 warnings · 2 issues · 24 informational
Audit score
F52/100
Needs work
- Agentic
- 84
- SEO
- 52
What we found
2Needs a fix20Could be better104Looks good24Informational- 1.Needs a fix: Your page has no main heading. see checkThe main heading gives visitors and search engines a clear topic.
- 2.Could be better: Interactive controls have source labels: needs attention. see checkA usable mobile layout helps visitors read and act on your content.
- 3.Could be better: Your images use older file formats. see checkEfficient image formats reduce download size.
- 4.Could be better: Anchor text is meaningful: needs attention. see checkWorking, descriptive links help people find the right page.
- 5.Could be better: Iframe usage: needs attention. see checkFaster pages help visitors reach your content sooner.
Built with 2 technologies· detected stack
Read from the public source and response headers of the sampled pages.
NginxServer
WordPressCMS / platform
A framework or CDN signal describes the public response, not the origin host or private backend.
Site checks
Every observation from the crawl, grouped by what it describes. Open a row for the evidence and the recommended fix.
Metadata11Looks good
100/100Looks good: Page title exists
Looks good · Metadata · Measured on your page
Observed evidence
Title found: "Home - The GitHub Blog"
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title length
Looks good · Metadata · Review suggested
Observed evidence
Title is 22 characters, inside this audit's 15–60 review range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Title says what the site does
Looks good · Metadata · Measured on your page
Observed evidence
Title "Home - The GitHub Blog" says more than the site name.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description exists
Looks good · Metadata · Measured on your page
Observed evidence
Meta description found: "Updates, ideas, and inspiration from GitHub to help developers build and design software."
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Meta description length
Looks good · Metadata · Review suggested
Observed evidence
Description is 89 characters and inside this audit's 70–160 preview range.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Titles unique across pages
Looks good · Metadata · Measured on your page
Observed evidence
All 10 indexable sampled pages have distinct titles.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: Homepage isn't noindexed
Looks good · Metadata · Measured on your page
Observed evidence
No blocking robots meta tag on the homepage.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Character encoding declared
Looks good · Metadata · Measured on your page
Observed evidence
UTF-8 declared in the Content-Type header and a meta tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: HTML5 doctype
Looks good · Metadata · Measured on your page
Observed evidence
HTML5 doctype declared.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta keywords tag
Looks good · Metadata · Measured on your page
Observed evidence
No obsolete meta keywords tag.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Valid metadata order in <head>
Looks good · Metadata · Measured on your page
Observed evidence
No invalid element interrupts metadata in <head>.
Why this matters
The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Indexing16Looks good
100/100Looks good: Single canonical declaration
Looks good · Indexing · Measured on your page
Observed evidence
One canonical declaration found.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Noindex and canonical agree
Looks good · Indexing · Measured on your page
Observed evidence
No conflicting noindex and cross-page canonical instructions.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No meta-refresh redirect
Looks good · Indexing · Measured on your page
Observed evidence
No meta-refresh redirect.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No soft-404 response
Looks good · Indexing · Measured on your page
Observed evidence
No soft-404 pattern on sampled HTTP 200 pages.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical target integrity
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is a valid https URL. Its host is checked by the canonical consistency check.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled URLs have aligned indexability signals
Looks good · Indexing · Measured on your page
Observed evidence
Indexability signals align across 10 sampled URL(s).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 10 more checks
Looks good: robots.txt exists
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt responds with 200.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: robots.txt doesn't block everything
Looks good · Indexing · Measured on your page
Observed evidence
The audited URL is allowed for Googlebot. No path rule matches this URL.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap exists
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap found at https://github.blog/sitemap_index.xml.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap parses and lists URLs
Looks good · Indexing · Measured on your page
Observed evidence
Sitemap lists 996 same-origin URLs.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sitemap declared in robots.txt
Looks good · Indexing · Measured on your page
Observed evidence
robots.txt declares the sitemap.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical URL set
Looks good · Indexing · Measured on your page
Observed evidence
Canonical set: https://github.blog/
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Canonical is absolute and self-referencing
Looks good · Indexing · Measured on your page
Observed evidence
Canonical is absolute and points at this page.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: www vs apex consistency
Looks good · Indexing · Measured on your page
Observed evidence
Hostname is used consistently (github.blog).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: URLs are readable slugs
Looks good · Indexing · Measured on your page
Observed evidence
URL slugs are readable (29 sampled).
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Sampled pages expose search-access signals
Looks good · Indexing · Measured on your page
Observed evidence
No restrictive search-access signal on 10 sampled page(s). Actual indexing is not verified.
Why this matters
These rules decide whether the page can be indexed at all. One wrong directive hides good work. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Content9Looks good2Informational
100/100Not measured: ReadabilityFlesch reading ease ≈ 23 — very difficult.
Not measured · Content · Not established
Observed evidence
Flesch reading ease ≈ 23 — very difficult.
Why this matters
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.
Recommended fix
Shorten sentences and prefer plain words. Aim for 50–70 for a general audience.
Not applicable: Title and H1 agreeNeed both a <title> and an H1 to compare them.
Not applicable · Content · Measured on your page
Observed evidence
Need both a <title> and an H1 to compare them.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. This check does not apply to the features observed in this sample.
Recommended fix
Add whichever is missing — the metadata and headings checks name it — then this check confirms the two describe the same topic.
Looks good: Crawlable content in source HTML
Looks good · Content · Measured on your page
Observed evidence
No recognized empty JavaScript application shell on 10 sampled page(s). The entered page exposes 1006 publisher word(s).
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage content volume
Looks good · Content · Measured on your page
Observed evidence
The audited page has about 1006 words of main content.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Text-to-HTML ratio
Looks good · Content · Measured on your page
Observed evidence
Text-to-HTML ratio is 7.3%.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No placeholder text
Looks good · Content · Measured on your page
Observed evidence
No placeholder text detected on crawled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 5 more checks
Looks good: No starter-template leftovers
Looks good · Content · Measured on your page
Observed evidence
No starter-template artifacts detected.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Crawled pages aren't near-duplicates
Looks good · Content · Measured on your page
Observed evidence
No near-duplicate main content among 10 indexable sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Outbound references
Looks good · Content · Measured on your page
Observed evidence
64 outbound link(s) present.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Discovery copy is distinct across sampled pages
Looks good · Content · Measured on your page
Observed evidence
No repeated description, H1, or publisher copy across 10 sampled pages.
Why this matters
This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Structured data5Looks good
100/100Looks good: JSON-LD present
Looks good · Structured data · Measured on your page
Observed evidence
3 JSON-LD block(s) found on the homepage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: JSON-LD parses
Looks good · Structured data · Measured on your page
Observed evidence
All 12 JSON-LD block(s) parse cleanly.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Organization or WebSite schema
Looks good · Structured data · Measured on your page
Observed evidence
Identity schema present: WebSite, Person.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content-specific schema
Looks good · Structured data · Measured on your page
Observed evidence
Content schema found: BlogPosting, TechArticle, CollectionPage, ProfilePage.
Why this matters
Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Headings1Needs a fix1Could be better3Looks good2Informational
12/100Needs a fix: H1 existsThe audited page has no <h1> (it starts at H2).
Needs a fix · Headings · Review suggestedCritical
Observed evidence
The audited page has no <h1> (it starts at H2).
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. Right now the sampled pages don't provide it.
Recommended fix
Add one <h1> stating what the page is about, usually the hero headline. Search engines, screen readers and answer engines use it as the page's main heading.
Could be better: Element IDs are unique per document20 duplicate ID occurrence(s) across 10 document(s).
Could be better · Headings · Measured on your page
Observed evidence
20 duplicate ID occurrence(s) across 10 document(s).
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. It is there, but weaker than this check expects.
Recommended fix
Give each element a unique id and update fragment links and aria-labelledby references to point to the intended element.
Affected pages (10)
- https://github.blog/
- https://github.blog/changelog/
- https://github.blog/ai-and-ml/
- https://github.blog/developer-skills/
- https://github.blog/engineering/
- https://github.blog/enterprise-software/
- https://github.blog/news-insights/
- https://github.blog/open-source/
- https://github.blog/security/
- https://github.blog/author/nickliffen/
Not applicable: Single H1No H1 exists to check for uniqueness.
Not applicable · Headings · Measured on your page
Observed evidence
No H1 exists to check for uniqueness.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.
Recommended fix
The H1 presence check covers the missing main heading.
Not applicable: H1 has real textNo H1 text exists to inspect.
Not applicable · Headings · Measured on your page
Observed evidence
No H1 text exists to inspect.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. This check does not apply to the features observed in this sample.
Recommended fix
The H1 presence check covers the missing main heading.
Looks good: Heading levels don't skip
Looks good · Headings · Measured on your page
Observed evidence
Heading hierarchy is sequential across 47 headings.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Headings are descriptive
Looks good · Headings · Measured on your page
Observed evidence
47 headings, averaging 5.9 words — descriptive.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is sectioned with H2s
Looks good · Headings · Measured on your page
Observed evidence
28 H2 section(s) structure the page.
Why this matters
Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Images1Could be better3Looks good
84/100Could be better: Modern image formats44 of 44 raster images are served only as PNG or JPEG: generic-github-copilot-logo-stripe.png, 4ba0cd42388a255e04c78e5143548f22e577d68e…, 4ba0cd42388a255e04c78e5143548f22e577d68e…, ….
Could be better · Images · Review suggested
Observed evidence
44 of 44 raster images are served only as PNG or JPEG: generic-github-copilot-logo-stripe.png, 4ba0cd42388a255e04c78e5143548f22e577d68e…, 4ba0cd42388a255e04c78e5143548f22e577d68e…, ….
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.
Recommended fix
Serve WebP or AVIF versions, which are usually 25–50% smaller at the same quality. Use <picture> with a WebP/AVIF <source> and the original as fallback, or an image CDN or framework image component that converts automatically.
Looks good: Alt text coverage
Looks good · Images · Measured on your page
Observed evidence
All 52 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Width/height attributes
Looks good · Images · Measured on your page
Observed evidence
All 52 visible images declare dimensions or are sized by their container.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Lazy loading
Looks good · Images · Measured on your page
Observed evidence
52/52 images are lazy-loaded.
Why this matters
Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Links2Could be better4Looks good
91/100Could be better: Anchor text is meaningful8 of 247 links have unclear anchor text: 8 generic ("Learn more").
Could be better · Links · Review suggested
Observed evidence
8 of 247 links have unclear anchor text: 8 generic ("Learn more").
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.
Recommended fix
Make each link say where it goes ("Read the pricing guide" rather than "Read more"). For icon-only links, add an aria-label. Anchor text tells crawlers and screen-reader users what the destination is about.
Affected pages (1)
- https://github.blog/
Could be better: External links use rel=noopener8 external link(s) open in a new tab without rel="noopener".
Could be better · Links · Review suggested
Observed evidence
8 external link(s) open in a new tab without rel="noopener".
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. It is there, but weaker than this check expects.
Recommended fix
Current browsers already treat target="_blank" as noopener, so the remaining risk is limited to older browsers. Adding rel="noopener" keeps the opened page from controlling yours there too.
Looks good: Internal links resolve
Looks good · Links · Measured on your page
Observed evidence
All 12 sampled internal links return < 400.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No dead placeholder links
Looks good · Links · Measured on your page
Observed evidence
No placeholder links on the audited page.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Homepage links into the site
Looks good · Links · Measured on your page
Observed evidence
Homepage links to 92 distinct internal pages.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Same-page links have source targets
Looks good · Links · Measured on your page
Observed evidence
11 same-page fragment link(s) have source targets.
Why this matters
Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Mobile1Could be better4Looks good1Informational
77/100Could be better: Interactive controls have source labels17 of 1125 source controls lack a detectable name.
Could be better · Mobile · Measured on your page
Observed evidence
17 of 1125 source controls lack a detectable name.
Why this matters
Google indexes the phone rendering, so that is the version being graded. It is there, but weaker than this check expects.
Recommended fix
Give each control visible text, a connected label, aria-label or aria-labelledby. Placeholder and neighboring text alone do not name an input. Verify the browser accessibility tree after fixing.
Affected pages (10)
- https://github.blog/
- https://github.blog/changelog/
- https://github.blog/ai-and-ml/
- https://github.blog/developer-skills/
- https://github.blog/engineering/
- https://github.blog/enterprise-software/
- https://github.blog/news-insights/
- https://github.blog/open-source/
- https://github.blog/security/
- https://github.blog/author/nickliffen/
Not measured: No tiny inline font sizesNo sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Not measured · Mobile · Not established
Observed evidence
No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.
Why this matters
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.
Recommended fix
Check computed font sizes in a browser across mobile widths.
Looks good: Viewport meta tag
Looks good · Mobile · Measured on your page
Observed evidence
Viewport configured: "width=device-width, initial-scale=1".
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Pinch zoom not disabled
Looks good · Mobile · Measured on your page
Observed evidence
The viewport lets users zoom.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Responsive image markup
Looks good · Mobile · Measured on your page
Observed evidence
55/59 images ship responsive srcset variants.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: ARIA references point to source elements
Looks good · Mobile · Measured on your page
Observed evidence
125 ARIA reference(s) resolve within their source documents. Rendered visibility was not tested.
Why this matters
Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Language2Looks good1Informational
100/100Not applicable: hreflang syntaxNo hreflang tags — fine for single-language sites.
Not applicable · Language · Measured on your page
Observed evidence
No hreflang tags — fine for single-language sites.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. This check does not apply to the features observed in this sample.
Recommended fix
Only add hreflang if you publish the same content in multiple languages/regions.
Looks good: html lang attribute
Looks good · Language · Measured on your page
Observed evidence
Language declared: lang="en-US".
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Declared language matches content
Looks good · Language · Measured on your page
Observed evidence
Declared language (en) matches detected content language.
Why this matters
The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Branding2Looks good2Informational
100/100Not measured: Web app manifestNo web manifest linked.
Not measured · Branding · Not established
Observed evidence
No web manifest linked.
Why this matters
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.
Recommended fix
Optional, but a manifest.json enables install prompts and better mobile integration.
Not measured: Theme colorNo theme-color meta tag.
Not measured · Branding · Not established
Observed evidence
No theme-color meta tag.
Why this matters
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.
Recommended fix
Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.
Looks good: Favicon
Looks good · Branding · Measured on your page
Observed evidence
Favicon declared via <link rel="icon"> (https://github.githubassets.com/favicon.ico).
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Apple touch icon
Looks good · Branding · Measured on your page
Observed evidence
apple-touch-icon is declared.
Why this matters
These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Performance
Measured from the audited response and its markup. These are source observations, not field Core Web Vitals.
| Measure | This site | Reading |
|---|---|---|
| Iframe usage | — | Could be better: needs attention5 iframes on the homepage. |
| Web fonts don't block text | — | Informational: not applicableNo Google Fonts stylesheet links detected. |
| Server response time | 108 ms | Looks good: goodThe audit received response headers after 108 ms from one test location. |
| HTML payload size | 283 KB | Looks good: goodThe page's HTML is 283 KB uncompressed: acceptable, though under 100 KB is a good target for content pages. |
| No render-blocking head scripts | — | Looks good: goodNo synchronous render-blocking scripts in <head>. |
| Inline styles are bounded | 43.8 KB | Looks good: goodInline styles total 43.8 KB. |
| Script/stylesheet count | — | Looks good: good13 total script/style resources — reasonable. |
| HTML served compressed | — | Looks good: goodHTML is compressed with br. |
| Source HTML weight | 283.1 KB | Informational: measured source, not transferred bytes283.1 KB of HTML on the audited page |
From a single automated fetch of the audited page. A quick reading, not a substitute for Lighthouse or field data.
Security
HTTPS, transport security and the response headers the audited pages send.
Could be better: X-Content-Type-OptionsX-Content-Type-Options: nosniff is not set.
Could be better · Security · Review suggested
Observed evidence
X-Content-Type-Options: nosniff is not set.
Why this matters
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.
Recommended fix
Add it — one header, stops MIME-sniffing attacks. Most hosts let you set headers in config (vercel.json, netlify.toml, next.config).
Could be better: Content Security PolicyNo Content-Security-Policy detected.
Could be better · Security · Review suggested
Observed evidence
No Content-Security-Policy detected.
Why this matters
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.
Recommended fix
Configure an enforced policy for script and resource origins; use report-only monitoring to prepare changes safely.
Could be better: Browser feature permissionsNo explicit restriction on sensitive browser features was observed.
Could be better · Security · Review suggested
Observed evidence
No explicit restriction on sensitive browser features was observed.
Why this matters
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.
Recommended fix
Disable unused camera, microphone, or geolocation access using Permissions-Policy.
Could be better: Server technology disclosureThe X-Powered-By header advertises "WordPress VIP <https://wpvip.com/>".
Could be better · Security · Review suggested
Observed evidence
The X-Powered-By header advertises "WordPress VIP <https://wpvip.com/>".
Why this matters
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.
Recommended fix
You can remove it (in Next.js: poweredByHeader: false; in Express: app.disable('x-powered-by')). It adds bytes to every response and tells scanners what to probe; it is not a vulnerability by itself.
Not applicable: Password forms avoid URL submissionNo enabled, named password inputs in sampled HTML.
Not applicable · Security · Measured on your page
Observed evidence
No enabled, named password inputs in sampled HTML.
Why this matters
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.
Recommended fix
Review authentication forms separately when applicable.
Looks good: Site serves over HTTPS
Looks good · Security · Measured on your page
Observed evidence
Site serves over HTTPS.
Why this matters
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.
Recommended fix
Nothing to do here.
Looks good: HTTP redirects to HTTPS
Looks good · Security · Measured on your page
Observed evidence
http:// permanently redirects to https://./
Why this matters
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.
Recommended fix
Nothing to do here.
Looks good: HSTS header
Looks good · Security · Measured on your page
Observed evidence
HSTS is set: max-age=31536000;includeSubdomains;preload.
Why this matters
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.
Recommended fix
Nothing to do here.
Looks good: Frame embedding protection
Looks good · Security · Measured on your page
Observed evidence
Response headers restrict cross-origin framing (X-Frame-Options SAMEORIGIN).
Why this matters
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.
Recommended fix
Nothing to do here.
Looks good: Referrer policy
Looks good · Security · Measured on your page
Observed evidence
No Referrer-Policy is set, so browsers apply their default, strict-origin-when-cross-origin, which sends only the origin to other sites.
Why this matters
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.
Recommended fix
Nothing to do here.
Looks good: No mixed content
Looks good · Security · Measured on your page
Observed evidence
No insecure subresources detected.
Why this matters
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.
Recommended fix
Nothing to do here.
Looks good: Declared form submission targets
Looks good · Security · Measured on your page
Observed evidence
31 declared form(s) submit over HTTPS. Some post to another site (https://s88570519.t.eloqua.com),/ which is normal for newsletter, payment and booking services; confirm each is one you use.
Why this matters
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.
Recommended fix
Nothing to do here.
AI answer readiness
Retrieval signals an answer engine relies on: crawler access, clear entities and answers it can quote. These checks do not measure citations or traffic.
Could be better: llms.txtNo /llms.txt file.
Could be better · AI answer readiness · Review suggested
Observed evidence
No /llms.txt file.
Why this matters
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.
Recommended fix
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.
Could be better: FAQ/QA schemaNo FAQPage or QAPage schema on any crawled page.
Could be better · AI answer readiness · Review suggested
Observed evidence
No FAQPage or QAPage schema on any crawled page.
Why this matters
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.
Recommended fix
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.
Could be better: Question-style headingsOnly 7% of 333 H2/H3 headings are question-shaped.
Could be better · AI answer readiness · Review suggested
Observed evidence
Only 7% of 333 H2/H3 headings are question-shaped.
Why this matters
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.
Recommended fix
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.
Could be better: Definitional openingThe opening paragraph doesn't define what the site/topic is: "Learn about artificial intelligence and machine learning across the GitHub ecosy…"
Could be better · AI answer readiness · Review suggested
Observed evidence
The opening paragraph doesn't define what the site/topic is: "Learn about artificial intelligence and machine learning across the GitHub ecosy…"
Why this matters
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.
Recommended fix
"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.
Could be better: Question headings have concise answers0/23 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Could be better · AI answer readiness · Measured on your page
Observed evidence
0/23 question-shaped heading(s) have a 20–500 character paragraph immediately after them.
Why this matters
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.
Recommended fix
Put a direct 20–500 character answer paragraph immediately after each question heading so retrieval systems can quote it cleanly.
Affected pages (5)
- https://github.blog/ai-and-ml/
- https://github.blog/engineering/
- https://github.blog/enterprise-software/
- https://github.blog/open-source/
- https://github.blog/security/
Could be better: Machine-readable provenance signalsOnly 3 of 4 provenance signal types were found: author, date, breadcrumb.
Could be better · AI answer readiness · Measured on your page
Observed evidence
Only 3 of 4 provenance signal types were found: author, date, breadcrumb.
Why this matters
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.
Recommended fix
Add the missing author, date, breadcrumb, or contact signal so machines can identify provenance and site structure.
Affected pages (10)
- https://github.blog/
- https://github.blog/changelog/
- https://github.blog/ai-and-ml/
- https://github.blog/developer-skills/
- https://github.blog/engineering/
- https://github.blog/enterprise-software/
- https://github.blog/news-insights/
- https://github.blog/open-source/
- https://github.blog/security/
- https://github.blog/author/nickliffen/
Could be better: Markdown copies of pagesNo markdown copy answered at /index.md or /changelog/index.md or /index.html.md.
Could be better · AI answer readiness · Measured on your page
Observed evidence
No markdown copy answered at /index.md or /changelog/index.md or /index.html.md.
Why this matters
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.
Recommended fix
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.
Affected pages (2)
- https://github.blog/
- https://github.blog/changelog/
Not measured: llms-full.txtNo /llms-full.txt.
Not measured · AI answer readiness · Not established
Observed evidence
No /llms-full.txt.
Why this matters
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.
Recommended fix
Optional companion to llms.txt containing your full content as one markdown file — useful for sites whose pages are JS-heavy.
Not measured: Citable facts density76 concrete figures across 2480 words.
Not measured · AI answer readiness · Not established
Observed evidence
76 concrete figures across 2480 words.
Why this matters
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.
Recommended fix
Good — keep facts specific and current, and date-stamp them.
Not measured: llms.txt links resolve to this siteNo readable llms.txt was available to inspect for Markdown links.
Not measured · AI answer readiness · Not established
Observed evidence
No readable llms.txt was available to inspect for Markdown links.
Why this matters
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.
Recommended fix
Publish a readable llms.txt, then link its important pages with same-origin Markdown URLs.
Not measured: llms.txt follows the specNo readable /llms.txt, so its structure cannot be checked.
Not measured · AI answer readiness · Not established
Observed evidence
No readable /llms.txt, so its structure cannot be checked.
Why this matters
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.
Recommended fix
Publish llms.txt first — the llms.txt check covers that — then this one verifies the structure.
Not applicable: Accept: text/markdown negotiationThe homepage answered Accept: text/markdown with text/html; charset=UTF-8.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
The homepage answered Accept: text/markdown with text/html; charset=UTF-8.
Why this matters
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.
Recommended fix
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.
Not applicable: Advertised machine interfaces are inspectableNo OpenAPI interface was advertised by sampled HTML.
Not applicable · AI answer readiness · Measured on your page
Observed evidence
No OpenAPI interface was advertised by sampled HTML.
Why this matters
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.
Recommended fix
An API is optional. Add a service-desc link if you already publish a machine-readable API specification.
Looks good: AI crawler access
Looks good · AI answer readiness · Measured on your page
Observed evidence
The audited URL is allowed for evaluated answer-search crawlers.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Semantic HTML structure
Looks good · AI answer readiness · Measured on your page
Observed evidence
Semantic structure present: main×1, article×21, section×3, nav×7, header×1, footer×22.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Answers lead the section
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs get to the point without preamble.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Content is chunkable
Looks good · AI answer readiness · Measured on your page
Observed evidence
Paragraphs average 12 words, lists present — chunk-friendly.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Freshness signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
dateModified present in schema.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Cites external sources
Looks good · AI answer readiness · Measured on your page
Observed evidence
555 outbound reference(s) across crawled pages.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Consistent brand entity
Looks good · AI answer readiness · Measured on your page
Observed evidence
Brand declared: og:site_name "The GitHub Blog" + identity schema.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Description reads as a liftable summary
Looks good · AI answer readiness · Measured on your page
Observed evidence
Meta description works as a standalone summary.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Entity identity agrees across signals
Looks good · AI answer readiness · Measured on your page
Observed evidence
The site is consistently named "The GitHub Blog" and 4 identity URL(s) stay on github.blog.
Why this matters
This is what an AI assistant relies on when deciding whether it can quote your page. The inspected source provides this signal.
Recommended fix
Nothing to do here.
AdSense readinessOptional
Publisher-policy signals, for sites that plan to carry ads. These checks do not affect the overall score or grade, and they do not measure or guarantee AdSense approval.
On its own, this site scores 28/100 for publisher readiness. Ignore this section if you do not run ads.
Needs a fix: Privacy policy pageNo privacy policy page is linked or crawlable.
Needs a fix · AdSense policy · Review suggestedCritical
Observed evidence
No privacy policy page is linked or crawlable.
Why this matters
A publisher review looks for this before it accepts a site. Right now the sampled pages don't provide it.
Recommended fix
Publish an accessible privacy policy that discloses cookies and data use by Google and other third-party ad vendors.
Could be better: Sampled publisher-content coverage1/10 editorial pages expose fewer than 250 publisher words; those 10 pages hold 6184 publisher words in total.
Could be better · AdSense policy · Review suggestedCritical
Observed evidence
1/10 editorial pages expose fewer than 250 publisher words; those 10 pages hold 6184 publisher words in total.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Review whether each page fully serves its purpose. Expand incomplete editorial content with useful information; keep concise navigation and tool pages when they help visitors.
Affected pages (1)
- https://github.blog/author/nickliffen/
Could be better: Terms pageNo terms of use page found.
Could be better · AdSense policy · Review suggested
Observed evidence
No terms of use page found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Consider adding terms that identify the service rules and publisher. This is a transparency heuristic, not an AdSense requirement.
Could be better: Contact methodNo contact page or mailto link found.
Could be better · AdSense policy · Review suggested
Observed evidence
No contact page or mailto link found.
Why this matters
A publisher review looks for this before it accepts a site. It is there, but weaker than this check expects.
Recommended fix
Add a working contact route or visible email so users can reach the publisher. This is a trust heuristic, not a published approval rule.
Not measured: Privacy policy advertising disclosuresA privacy page was not present in the crawl sample, so its disclosures could not be verified.
Not measured · AdSense policy · Not established
Observed evidence
A privacy page was not present in the crawl sample, so its disclosures could not be verified.
Why this matters
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.
Recommended fix
Confirm the policy explains cookies or similar storage, Google or advertising vendors, and third-party data use.
Not measured: First-party contact emailA contact page or form exists, but no public email address was found.
Not measured · AdSense policy · Review suggested
Observed evidence
A contact page or form exists, but no public email address was found.
Why this matters
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.
Recommended fix
A public email is optional. The separate contact-method check covers whether readers have a way to reach the publisher.
Not measured: ads.txtNo ads.txt yet.
Not measured · AdSense policy · Not established
Observed evidence
No ads.txt yet.
Why this matters
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.
Recommended fix
When AdSense provides your publisher entry, publish it exactly at /ads.txt and monitor authorization status in your account.
Not measured: Domain age & historyDomain age isn't visible from the site itself.
Not measured · AdSense policy · Not established
Observed evidence
Domain age isn't visible from the site itself.
Why this matters
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.
Recommended fix
Do not use age as a content-quality proxy. Verify ownership and account eligibility in AdSense; Google's general eligibility page publishes no domain-age threshold.
Not measured: Latest article has real depthNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
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.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reads the newest one.
Not measured: Latest article reads as edited workNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
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.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then reviews its style signals.
Not measured: Latest article names an author and a dateNo article-shaped page was found on this site, so there is nothing to read.
Not measured · AdSense policy · Not established
Observed evidence
No article-shaped page was found on this site, so there is nothing to read.
Why this matters
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.
Recommended fix
Publish articles under a path such as /blog/… and list them in the sitemap. This check then looks for its byline and date.
Looks good: About page
Looks good · AdSense policy · Measured on your page
Observed evidence
About page found: https://github.blog/news-insights/company-news/10-technical-talks-im-excited-about-at-github-universe-2026/
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Thin page share
Looks good · AdSense policy · Review suggested
Observed evidence
10/10 editorial pages clear the audit's publisher-content triage threshold.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No ads on non-content screens
Looks good · AdSense policy · Published platform rule
Observed evidence
No Google ad code detected on sampled non-content screens.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Tool pages expose explanatory content
Looks good · AdSense policy · Review suggested
Observed evidence
All 10 sampled tool-style screens include crawlable explanation.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content differs across URLs
Looks good · AdSense policy · Review suggested
Observed evidence
No high publisher-content repetition among 9 substantial sampled page(s).
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Publisher content exists in source HTML
Looks good · AdSense policy · Measured on your page
Observed evidence
No empty client-rendered publisher shell in the crawl sample.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Article-style content exists
Looks good · AdSense policy · Measured on your page
Observed evidence
Article-style content detected.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: No "coming soon" or placeholder pages
Looks good · AdSense policy · Measured on your page
Observed evidence
No "coming soon", "under construction" or lorem-ipsum text on crawled pages.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Site language is AdSense-supported
Looks good · AdSense policy · Measured on your page
Observed evidence
Language "en" is AdSense-supported.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Show 4 more checks
Looks good: Policy pages linked site-wide
Looks good · AdSense policy · Measured on your page
Observed evidence
All 10 crawled pages link to the privacy policy.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Looks good: Existing ad scripts
Looks good · AdSense policy · Measured on your page
Observed evidence
No competing ad scripts on the page.
Why this matters
A publisher review looks for this before it accepts a site. The inspected source provides this signal.
Recommended fix
Nothing to do here.
Hosting and infrastructure
Public endpoint facts observed at audit time. A CDN or proxy can conceal the origin infrastructure.
| Hostname | github.blog |
|---|---|
| Server | Nginx |
| IP addresses | 192.0.66.2 |
| DNS A | 192.0.66.2 |
| DNS NS | dns3.p05.nsone.net · dns1.p05.nsone.net · dns2.p05.nsone.net · dns4.p05.nsone.net |
| DNS CAA | {"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"sectigo.com"} |
| TLS | TLSv1.3TLS_AES_128_GCM_SHA256 |
| Certificate issuer | Let's Encrypt / YE2 |
| Certificate valid until | Jan 26 19:45:13 2027 GMT |
| Certificate validation | Passed |
Website anatomy and diagnostics
Explore links, resources, crawler access and site integrations.
Page architecture
Choose a page to explore its details and connections.
Page content
1006 publisher words
Page structure
html content
Observed discovery
Depth 0 · 9 incoming links
HTTP 200 · 283.1 KB source
Source interactions
148 controls · 1 unnamed
11 script / 2 stylesheet references
- Canonical declaration
- https://github.blog/
- Schema types
- TechArticle, Person, WebPage, BlogPosting, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification
- Outgoing links in sampled graph
- /changelog/ · /ai-and-ml/ · /ai-and-ml/generative-ai/ · /ai-and-ml/github-copilot/ · /ai-and-ml/llms/ · /ai-and-ml/machine-learning/ · /ai-and-ml/generative-ai/how-ai-code-generation-works/ · /developer-skills/ · /developer-skills/application-development/ · /developer-skills/career-growth/ · /developer-skills/github/ · /developer-skills/github-education/ · /developer-skills/programming-languages-and-frameworks/ · /engineering/ · /engineering/architecture-optimization/ · /engineering/engineering-principles/ · /engineering/infrastructure/ · /engineering/platform-security/ · /engineering/user-experience/ · /engineering/how-we-use-github-to-be-more-productive-collaborative-and-secure/ · /enterprise-software/ · /enterprise-software/automation/ · /enterprise-software/ci-cd/ · /enterprise-software/collaboration/ · /enterprise-software/devops/ · /enterprise-software/devsecops/ · /enterprise-software/governance-and-compliance/ · /news-insights/ · /news-insights/company-news/ · /news-insights/product-news/ · /news-insights/octoverse/ · /news-insights/policy-news-and-insights/ · /news-insights/research/ · /news-insights/the-library/ · /ai-and-ml/llms/unlocking-the-power-of-unstructured-data-with-rag/ · /open-source/ · /open-source/git/ · /open-source/maintainers/ · /open-source/social-impact/ · /open-source/gaming/ · /security/ · /security/application-security/ · /security/supply-chain-security/ · /security/vulnerability-research/ · /security/web-application-security/ · /ai-and-ml/github-copilot/beyond-code-generation-a-developers-guide-to-agentic-engineering/ · /author/nickliffen/ · /author/pholleran/ · /engineering/architecture-optimization/inside-githubs-new-git-storage-architecture/ · /author/kramanmsfteng/ · /author/bcelenza/ · /open-source/maintainers/accessibility-statements-now-have-a-home-on-github/ · /author/janmaartena11y-2-2-2-2-2-2-2-2/ · /open-source/maintainers/arnis-turns-any-place-on-earth-into-a-minecraft-world/ · /author/evillollive/ · /latest/ · /open-source/gaming/game-off-2026-the-theme-is-shift/ · /author/leereilly/ · /news-insights/company-news/github-universe-2026-evolving-every-layer-of-the-stack/ · /author/jayparikh/ · /news-insights/octoverse/octoverse-commits-pushes-reach-new-highs-in-2026-as-developers-build-with-agents/ · /author/staff/ · /news-insights/product-news/raising-the-bar-for-software-security-github-2fa-begins-march-13/ · /author/lauraleap/ · /author/hpsin/ · /changelog/2026-11-06-copilot-code-review-api-management-and-review-overview-updates · /changelog/2026-11-06-copilot-impact-dashboard-adds-chat-and-vs-code-agent-usage · /changelog/2026-11-06-github-copilot-weekly-releases-november-2 · /changelog/2026-11-06-github-copilot-in-slack-and-teams-is-generally-available · /engineering/architecture-optimization/the-bridge-to-agent-scale-git-infrastructure/ · /author/nellwhite/ · /author/vdye/ · /engineering/platform-security/staying-evergreen-how-we-automated-secure-access-and-repo-hygiene-in-a-shared-org/ · /author/callmegreg/ · /engineering/architecture-optimization/from-2500-requests-to-24-rebuilding-star-history-without-the-stargazers/ · /author/taylorcuilty/ · /author/saritai/ · /engineering/architecture-optimization/building-git-infrastructure-for-agent-scale-development/ · /engineering/architecture-optimization/improving-site-performance-by-shipping-more-css/ · /author/joshblack/ · /author/francinelucca/ · /news-insights/company-news/the-next-developer-interface-is-ambient-intelligence/ · /author/martinwoodward/ · /news-insights/company-news/github-availability-report-september-2026/ · /author/jakuboleksy/ · /news-insights/company-news/10-technical-talks-im-excited-about-at-github-universe-2026/ · /author/andreagriffiths11/ · /news-insights/policy-news-and-insights/developer-policy-update-transparency-state-policy-and-whats-ahead/ · /author/margarettucker/ · /news-insights/research/developers-want-more-efficient-software-heres-what-over-1000-github-users-told-us-they-need/ · /author/paullyoung/ · /news-insights/company-news/github-availability-report-august-2026/
Routes: / · /changelog · /ai-and-ml · /developer-skills · /engineering · /enterprise-software · /news-insights · /open-source · /security · /author
Resource origins 8
Resources associated with your website. External resources may belong to the same organization.
- https://github.blog/stylesheet, image, script · 360 references · same origin
- https://www.youtube.com/frame · 22 references · cross origin
- https://avatars.githubusercontent.com/image · 14 references · cross origin
- https://ghcc.githubassets.com/script · 10 references · cross origin
- https://js.monitor.azure.com/script · 10 references · cross origin
- https://analytics.githubassets.com/script · 10 references · cross origin
- https://stats.wp.com/script · 10 references · cross origin
- https://blog-github-com-preprod.go-vip.net/image · 1 references · cross origin
Crawler policy by page
Review crawler access for your pages. Search, training and user-triggered services have different purposes; declared access does not guarantee discovery.
| Crawler / purpose | Page | Policy | Matched directive |
|---|---|---|---|
| Googlebotsearch | / | allowed | Declared policy for this page. |
| Googlebotsearch | /changelog/ | allowed | Declared policy for this page. |
| Googlebotsearch | /ai-and-ml/ | allowed | Declared policy for this page. |
| Googlebotsearch | /developer-skills/ | allowed | Declared policy for this page. |
| Googlebotsearch | /engineering/ | allowed | Declared policy for this page. |
| Googlebotsearch | /enterprise-software/ | allowed | Declared policy for this page. |
| Googlebotsearch | /news-insights/ | allowed | Declared policy for this page. |
| Googlebotsearch | /open-source/ | allowed | Declared policy for this page. |
| Googlebotsearch | /security/ | allowed | Declared policy for this page. |
| Googlebotsearch | /author/nickliffen/ | allowed | Declared policy for this page. |
| bingbotsearch | / | allowed | Declared policy for this page. |
| bingbotsearch | /changelog/ | allowed | Declared policy for this page. |
| bingbotsearch | /ai-and-ml/ | allowed | Declared policy for this page. |
| bingbotsearch | /developer-skills/ | allowed | Declared policy for this page. |
| bingbotsearch | /engineering/ | allowed | Declared policy for this page. |
| bingbotsearch | /enterprise-software/ | allowed | Declared policy for this page. |
| bingbotsearch | /news-insights/ | allowed | Declared policy for this page. |
| bingbotsearch | /open-source/ | allowed | Declared policy for this page. |
| bingbotsearch | /security/ | allowed | Declared policy for this page. |
| bingbotsearch | /author/nickliffen/ | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | / | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /changelog/ | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /ai-and-ml/ | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /developer-skills/ | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /engineering/ | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /enterprise-software/ | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /news-insights/ | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /open-source/ | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /security/ | allowed | Declared policy for this page. |
| OAI-SearchBotsearch | /author/nickliffen/ | allowed | Declared policy for this page. |
| PerplexityBotsearch | / | allowed | Declared policy for this page. |
| PerplexityBotsearch | /changelog/ | allowed | Declared policy for this page. |
| PerplexityBotsearch | /ai-and-ml/ | allowed | Declared policy for this page. |
| PerplexityBotsearch | /developer-skills/ | allowed | Declared policy for this page. |
| PerplexityBotsearch | /engineering/ | allowed | Declared policy for this page. |
| PerplexityBotsearch | /enterprise-software/ | allowed | Declared policy for this page. |
| PerplexityBotsearch | /news-insights/ | allowed | Declared policy for this page. |
| PerplexityBotsearch | /open-source/ | allowed | Declared policy for this page. |
| PerplexityBotsearch | /security/ | allowed | Declared policy for this page. |
| PerplexityBotsearch | /author/nickliffen/ | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | / | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /changelog/ | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /ai-and-ml/ | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /developer-skills/ | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /engineering/ | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /enterprise-software/ | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /news-insights/ | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /open-source/ | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /security/ | allowed | Declared policy for this page. |
| Claude-SearchBotsearch | /author/nickliffen/ | allowed | Declared policy for this page. |
| GPTBottraining | / | allowed | Declared policy for this page. |
| GPTBottraining | /changelog/ | allowed | Declared policy for this page. |
| GPTBottraining | /ai-and-ml/ | allowed | Declared policy for this page. |
| GPTBottraining | /developer-skills/ | allowed | Declared policy for this page. |
| GPTBottraining | /engineering/ | allowed | Declared policy for this page. |
| GPTBottraining | /enterprise-software/ | allowed | Declared policy for this page. |
| GPTBottraining | /news-insights/ | allowed | Declared policy for this page. |
| GPTBottraining | /open-source/ | allowed | Declared policy for this page. |
| GPTBottraining | /security/ | allowed | Declared policy for this page. |
| GPTBottraining | /author/nickliffen/ | allowed | Declared policy for this page. |
| ClaudeBottraining | / | allowed | Declared policy for this page. |
| ClaudeBottraining | /changelog/ | allowed | Declared policy for this page. |
| ClaudeBottraining | /ai-and-ml/ | allowed | Declared policy for this page. |
| ClaudeBottraining | /developer-skills/ | allowed | Declared policy for this page. |
| ClaudeBottraining | /engineering/ | allowed | Declared policy for this page. |
| ClaudeBottraining | /enterprise-software/ | allowed | Declared policy for this page. |
| ClaudeBottraining | /news-insights/ | allowed | Declared policy for this page. |
| ClaudeBottraining | /open-source/ | allowed | Declared policy for this page. |
| ClaudeBottraining | /security/ | allowed | Declared policy for this page. |
| ClaudeBottraining | /author/nickliffen/ | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | / | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /changelog/ | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /ai-and-ml/ | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /developer-skills/ | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /engineering/ | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /enterprise-software/ | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /news-insights/ | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /open-source/ | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /security/ | allowed | Declared policy for this page. |
| Google-Extendedtraining and other Google AI uses | /author/nickliffen/ | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | / | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /changelog/ | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /ai-and-ml/ | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /developer-skills/ | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /engineering/ | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /enterprise-software/ | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /news-insights/ | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /open-source/ | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /security/ | allowed | Declared policy for this page. |
| ChatGPT-Useruser-initiated; robots may not apply | /author/nickliffen/ | allowed | Declared policy for this page. |
Advertised APIs and machine interfaces
No supported machine interfaces were advertised in the sampled HTML. An API or MCP server is optional; undiscovered interfaces remain unknown.
Public DNS and TLS endpoint
github.blog · observed · 192.0.66.2
- A
- 192.0.66.2
- AAAA
- Unavailable for this exact hostname
- CNAME
- Unavailable for this exact hostname
- NS
- dns3.p05.nsone.net · dns1.p05.nsone.net · dns2.p05.nsone.net · dns4.p05.nsone.net
- MX
- Unavailable for this exact hostname
- CAA
- {"critical":0,"type":"CAA","issue":"letsencrypt.org"} · {"critical":0,"type":"CAA","issue":"sectigo.com"}
TLS: TLSv1.3
Certificate validation passed for the observed endpoint.
Issuer: Let's Encrypt / YE2
Certificate valid until: Jan 26 19:45:13 2027 GMT
PageSpeed measurement
Loading the PageSpeed panel…
Growth resources
Loading growth resources…
Where to take this site next
Follow-on work suggested by the observations above.
- 01
Your top fixes list is the priority order — clear the red items before creating more content.
- 02
Re-run the combined audit after each batch of fixes
Re-run after fixes to see which checks changed; score bands are guidance, not a guarantee of ranking, traffic, or approval.
- 03
Make policy pages, publisher disclosures and substantial content reachable before applying. This audit cannot predict approval.
Apply the recommended fixes
Hand the complete evidence to a coding agent, or take the report with you.
Report notes
- 01This report covers the sampled public pages listed above. Other pages may have different results.
- 02Browser-rendered content, private backend systems and authenticated experiences may require a separate review.
- 03Unavailable observations are identified in the report. Results do not guarantee rankings, citations, security, accessibility or advertising approval.
Pages included in this report
- https://github.blog/
- https://github.blog/changelog/
- https://github.blog/ai-and-ml/
- https://github.blog/developer-skills/
- https://github.blog/engineering/
- https://github.blog/enterprise-software/
- https://github.blog/news-insights/
- https://github.blog/open-source/
- https://github.blog/security/
- https://github.blog/author/nickliffen/