Migration Report: reactjs.org to react.dev
React documentation (public)
2026-10-23 13:26 / 2026-10-23_131318
Crawl data: legacy.reactjs.org (old docs, kept online) 2026-10-23_131318 / react.dev (new docs) 2026-10-23_131318
Executive Summary
At Risk

14 of 97 old pages carried over; 14 improved, 0 got worse, and 83 have no counterpart.

Migration health: At Risk, based on 97 old pages and 100 pages crawled from react.dev (new docs); 86 pages exist only on the new site.

Set aside before analysis: 3 old pages that failed to load.

Note: The crawl of the new site stopped at 100 pages, so "no counterpart" means none was found among the pages crawled.

Note: The crawl of the old site stopped at 100 pages; old pages beyond that were not compared.

Note: 3 page matchs below 70% confidence are left out of the What Changed counts.

What we found
  1. 14 of 97 old pages have a counterpart on the new site; no counterpart was found for 83 among the 100 pages crawled from the new site. See evidence(Missing Pages tab)
    e.g. /blog/2016/02/19/new-versioning-scheme.html, /blog/2016/07/13/mixins-considered-harmful.html, /blog/2017/07/26/error-handling-in-react-16.html and 80 more
  2. 99 of 100 pages on the new site have no meta description, leaving search engines to choose snippet text on their own. See evidence(Findings tab)
    e.g. /blog, /blog/2021/06/08/the-plan-for-react-18, /blog/2022/03/08/react-18-upgrade-guide and 96 more
  3. All 100 pages on the new site carry no structured data (JSON-LD). See evidence(Findings tab)
    e.g. /, /blog, /blog/2021/06/08/the-plan-for-react-18 and 97 more
  4. 11 of 11 matched pages changed at least one search signal (title, description, headings, canonical, indexability or markup); 2 carry red flags. See evidence(What Changed tab)
  5. UA-41298772-1 (Universal Analytics) was replaced by G-B1E83PJ3RT (Google Analytics 4). Universal Analytics stopped processing data on July 1, 2023. See evidence(Dashboard tab)
Fix first
  1. Add meta descriptions (99 pages) See evidence(Findings tab)
  2. Add structured data (JSON-LD) to key pages (100 pages) See evidence(Findings tab)
  3. Choose redirect targets for 1 old URL; shorten 1 redirect chain See evidence(Old URL Check tab)

Working well: 14 matched pages improved, the SEO Strategy & Reach score rose from 25 to 44, and internal links on the new site are 100% HTTPS. 11 of 11 matched pages gained social preview tags. 96 of 97 checked old URLs reach a live page (95 cleanly).

100
Pages Crawled
654
Total Issues
99
Pre-Launch Priority
283
Recommended
2533
Implemented Well
14.4%
Page Match Rate
At Risk
Migration Health
Site Health Metrics

Cross-page analysis of SEO fundamentals across the destination site.

Unique Titles 99.0%
1 duplicate group
Schema Coverage 0.0%
Pages with JSON-LD structured data
Alt Text Coverage 91.3%
401 of 439 images
HTTPS Links 100.0%
Internal links using secure protocol
Avg Word Count 2687
2 thin pages (<300 words)
Avg Response 102ms
Server response time average
Thin Pages 2
2.0% of pages under 300 words
Orphan Pages 0
Pages with no inbound internal links
Migration Assessment
14
Pages Improved
0
Pages Unchanged
0
Pages Degraded
83
Pages Missing
Metric legacy.reactjs.org (old docs, kept online) react.dev (new docs) Change
Total Pages 100 100 No change
Total Issues 732 654 -78
Priority Issues 96 99 +3
Site Health At Risk At Risk
SEO Strategy & Reach
legacy.reactjs.org (old docs, kept online)
25/100
Weak
react.dev (new docs)
44/100
Basic
legacy.reactjs.org (old docs, kept online)
📍 Location: ,
🗺 Service Area: Unknown
react.dev (new docs)
📍 Location: ,
🗺 Service Area: Unknown
Geographic Reach 0/20 → 0/20 --
Scoring Methodology ▶
legacy.reactjs.org (old docs, kept online)
Sub-ScorePointsWhat Was Measured
Geo Page Coverage 0/4 No geo-targeted pages found
Market-Relative Coverage 0/4 0 geo pages (unknown market expects 8+)
Content Localization 0/4 no geo pages to assess
NAP & Local Schema 0/4 No phone or LocalBusiness schema found
Service Area Strategy 0/4 No geographic targeting strategy detected
react.dev (new docs)
Sub-ScorePointsWhat Was Measured
Geo Page Coverage 0/4 No geo-targeted pages found
Market-Relative Coverage 0/4 0 geo pages (unknown market expects 8+)
Content Localization 0/4 no geo pages to assess
NAP & Local Schema 0/4 No phone or LocalBusiness schema found
Service Area Strategy 0/4 No geographic targeting strategy detected
Scoring Criteria:
  • Geo Page Coverage: Raw count of dedicated geo-targeted pages. 0 pages = 0, 1-3 = 1, 4-7 = 2, 8-15 = 3, 16+ = 4.
  • Market-Relative Coverage: Geo pages relative to market size. is a unknown market (expects 8+ pages for full score). Thresholds: <10% = 0, 10-29% = 1, 30-59% = 2, 60-99% = 3, 100%+ = 4.
  • Content Localization: Measures whether geo pages contain genuine local content or are template copies with only city names swapped. Additive scoring: +1 if titles >80% unique, +1 if descriptions >50% unique, +1 if headings mention city names, +1 if word counts vary >15%.
  • NAP & Local Schema: Business identity signals. No NAP = 0, phone only = 1, LocalBusiness schema but inconsistent NAP = 2, consistent NAP + schema = 3, consistent NAP + schema ON geo pages = 4.
  • Service Area Strategy: How strategic is the geographic targeting? No strategy = 0, only listing page = 1, <30% suburb coverage = 2, 30-60% = 3, >60% = 4. Multi-state presence can boost by +1.
Service Depth 0/20 → 16/20 ▲ +16
Scoring Methodology ▶
legacy.reactjs.org (old docs, kept online)
Sub-ScorePointsWhat Was Measured
Service pages 0/None 0 pages
Content-rich (300+ words) 0/0 0 of 0
With review schema 0/0 0 of 0
react.dev (new docs)
Sub-ScorePointsWhat Was Measured
Service pages 6/None 6 pages
Content-rich (300+ words) 5/6 5 of 6
With review schema 0/6 0 of 6
Content Authority 14/20 → 16/20 ▲ +2
Scoring Methodology ▶
legacy.reactjs.org (old docs, kept online)
Sub-ScorePointsWhat Was Measured
Avg word count 4/4 1694 words (content pages)
Meta description coverage 0/4 0% (0/100)
Title uniqueness 4/4 97.8% unique
H1 quality 4/4 93% of pages have exactly 1 H1
Content uniqueness 2/4 2 near-duplicate group(s)
react.dev (new docs)
Sub-ScorePointsWhat Was Measured
Avg word count 4/4 2687 words (content pages)
Meta description coverage 0/4 1% (1/100)
Title uniqueness 4/4 99.0% unique
H1 quality 4/4 99% of pages have exactly 1 H1
Content uniqueness 4/4 0 near-duplicate group(s)
Technical Foundation 7/20 → 8/20 ▲ +1
Scoring Methodology ▶
legacy.reactjs.org (old docs, kept online)
Sub-ScorePointsWhat Was Measured
Sitemap coverage 0/4 0% (0/100)
Schema coverage 0/4 0.0% coverage
Meta tag coverage 0/4 0% have title+desc+canonical
Indexation health 4/4 0 noindex, 0 bad canonical
Performance & security 3/4 HTTPS: 93%, avg response: 81ms, HSTS: yes
react.dev (new docs)
Sub-ScorePointsWhat Was Measured
Sitemap coverage 0/4 0% (0/100)
Schema coverage 0/4 0.0% coverage
Meta tag coverage 0/4 1% have title+desc+canonical
Indexation health 4/4 0 noindex, 0 bad canonical
Performance & security 4/4 HTTPS: 100%, avg response: 102ms, HSTS: yes
Competitive Positioning 4/20 → 4/20 --
Scoring Methodology ▶
legacy.reactjs.org (old docs, kept online)
Sub-ScorePointsWhat Was Measured
Brand consistency 0/4 0% of titles
Review signals 0/4 0 pages, 0 reviews
Local business signals 0/4 0 pages, 0 complete
Internal linking 4/4 avg 63.4 links/page
Differentiated content 0/4 0 schema types, FAQ: no
react.dev (new docs)
Sub-ScorePointsWhat Was Measured
Brand consistency 0/4 0% of titles
Review signals 0/4 0 pages, 0 reviews
Local business signals 0/4 0 pages, 0 complete
Internal linking 4/4 avg 76.7 links/page
Differentiated content 0/4 0 schema types, FAQ: no
Strategy Impact: 19 points (▲ improvement)
Why does this matter? ▶

What the Strategy & Reach Score Means for Publishers

For a blog, documentation site or publication, content is the product, so the score reads a little differently than it does for a business site:

Topic depth. The Service Depth dimension counts dedicated, substantial pages for each topic, guide or section. Pillar pages that cover a subject thoroughly and link out to related articles rank better, and keep readers longer, than a flat stream of posts.

Content authority. Unique titles and descriptions, one clear H1 per page, substantial articles and no near-duplicate pages (tag archives, printer versions, syndicated copies) are the core of a publisher's search visibility.

Trust signals. A consistent brand in page titles, Organization and Article structured data, author and about pages, FAQ markup where it fits and rich internal linking between related pieces help search engines and readers judge the content as credible.

Technical foundation. An XML sitemap that covers every article, canonical URLs on syndicated or paginated content, noindex used only where intended, HTTPS and fast pages make sure new work is found and indexed quickly.

Geographic reach matters mainly to local news and regional publications; for other publishers it is informational.

Together, these show whether a site is built to earn search traffic across its topics, or relies on visitors who already know where to look.

Issue Breakdown by Severity
Severity Count Description
Implemented Well 2533 SEO best practices properly implemented. Great work!
Pre-Launch Priority 99 Issues that directly impact SEO rankings or user experience and should be addressed before launch.
Recommended 283 Improvements that would strengthen the site's search presence and overall quality.
Informational 272 Minor observations and nice-to-have improvements for reference.
Site-Level Checks

5 checks: 1 pass, 3 warn, 1 info. Checks on react.dev (new docs); analytics and verification tags compared with legacy.reactjs.org (old docs, kept online). Based on what Webtrace can see from outside the site (24 extra requests).

Status Check Finding
Warn One canonical address
http://www.react.dev takes 2 redirects to reach https://react.dev.
https://react.dev/ (200); HSTS on
  • Pass https://www.react.dev reaches https://react.dev in one permanent redirect.
    https://www.react.dev/ -> 308 -> https://react.dev/ (200)
  • Pass http://react.dev reaches https://react.dev in one permanent redirect.
    http://react.dev/ -> 308 -> https://react.dev/ (200)
  • Warn http://www.react.dev takes 2 redirects to reach https://react.dev.
    http://www.react.dev/ -> 308 -> https://www.react.dev/ -> 308 -> https://react.dev/ (200)
  • Pass Deep links on https://www.react.dev keep their path.
    https://www.react.dev/blog -> 308 -> https://react.dev/blog (200)
  • Pass Deep links on http://react.dev keep their path.
    http://react.dev/blog -> 308 -> https://react.dev/blog (200)
  • Pass Deep links on http://www.react.dev keep their path.
    http://www.react.dev/blog -> 308 -> https://www.react.dev/blog -> 308 -> https://react.dev/blog (200)
What to do: Send http://www.react.dev to https://react.dev with one permanent (301 or 308) redirect that keeps the path.
Pass Unknown URLs return 404
An address that does not exist answers 404 (Not Found).
https://react.dev/webtrace-soft-404-check-c164550bfb20/ -> 308 -> https://react.dev/webtrace-soft-404-check-c164550bfb20 (404)
  • Pass An address that does not exist answers 404 (Not Found).
    https://react.dev/webtrace-soft-404-check-c164550bfb20/ -> 308 -> https://react.dev/webtrace-soft-404-check-c164550bfb20 (404)
Warn Discovery files (robots.txt and sitemap)
No XML sitemap was found at the standard addresses, and robots.txt declares none.
https://react.dev/robots.txt (200, 24 bytes, 0 Sitemap lines)
  • Pass robots.txt loads (200).
    https://react.dev/robots.txt (200, 24 bytes, 0 Sitemap lines)
  • Warn No XML sitemap was found at the standard addresses, and robots.txt declares none.
    https://react.dev/sitemap.xml (404)
    https://react.dev/sitemap_index.xml (404)
    https://react.dev/wp-sitemap.xml (404)
What to do: Publish an XML sitemap and declare it in robots.txt with a Sitemap: line.
Warn Analytics tags
UA-41298772-1 (Universal Analytics) was replaced by G-B1E83PJ3RT (Google Analytics 4). Universal Analytics stopped processing data on July 1, 2023.
UA-41298772-1 (Universal Analytics): Changed to G-B1E83PJ3RT
TagBeforeAfterChange
UA-41298772-1 (Universal Analytics)100% (90/90)G-B1E83PJ3RT 100% (100/100)Changed to G-B1E83PJ3RT
What to do: Confirm the new property is intended, and annotate the switch date in analytics so trend lines are read correctly.
Info Ownership verification tags
google-site-verification was added to the homepage.
google-site-verification: Added
TagBeforeAfterChange
google-site-verification--sIlAGs... (43 characters)Added

What these checks cannot see: Search Console ownership verified by DNS record, HTML file, Google Analytics or Tag Manager; analytics sent from the server or added later by JavaScript or a consent tool; redirects that depend on cookies, location or the visitor's browser; anything behind a login. Probe requests identify themselves as WebtraceBot and follow robots.txt.

Page-by-Page Audit (100 pages)
URL Title Status Words Issues Health
▶/ React 200 1436 9 Needs Attention
  1. Recommended META: Description too long (260 chars, recommended max 160)
    The meta description is 260 characters. Search engines typically show up to 160 characters. A shorter description ensures the full snippet is visible.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 24 of 43 images missing alt text
    Some images are missing alt text (24 of 43 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 40 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (40 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Informational META: Title too short (5 chars, recommended min 30)
    The title tag is only 5 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational MULTIPLE H1: 2 H1 tags found
    This page has more than one H1 heading. While not critical, using a single H1 helps search engines understand the page's primary topic more clearly.
  8. Informational CONTENT: Very low text-to-HTML ratio (3.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (266 KB, recommended <100KB)
    The page weighs 266 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/state-as-a-snapshot State as a Snapshot – React 200 2359 9 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 6 of 7 images missing alt text
    Some images are missing alt text (6 of 7 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended ACCESSIBILITY: 6 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (6 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  6. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  7. Informational META: Title too short (27 chars, recommended min 30)
    The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  8. Informational CONTENT: Very low text-to-HTML ratio (5.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  9. Informational PERFORMANCE: Large page (227 KB, recommended <100KB)
    The page weighs 227 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/adding-interactivity Adding Interactivity – React 200 2886 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 3 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (3 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (4.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (297 KB, recommended <100KB)
    The page weighs 297 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/react-developer-tools React Developer Tools – React 200 514 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 2 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (2 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational META: Title too short (29 chars, recommended min 30)
    The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (107 KB, recommended <100KB)
    The page weighs 107 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/render-and-commit Render and Commit – React 200 1314 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 7 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (7 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (4.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (167 KB, recommended <100KB)
    The page weighs 167 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/thinking-in-react Thinking in React – React 200 4277 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 2 of 3 images missing alt text
    Some images are missing alt text (2 of 3 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (278 KB, recommended <100KB)
    The page weighs 278 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/tutorial-tic-tac-toe Tutorial: Tic-Tac-Toe – React 200 16585 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 16 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (16 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational META: Title too short (29 chars, recommended min 30)
    The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  7. Informational CONTENT: Very low text-to-HTML ratio (8.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (940 KB, recommended <100KB)
    The page weighs 940 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/useactionstate useActionState – React 200 5150 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (475 KB, recommended <100KB)
    The page weighs 475 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/usecallback useCallback – React 200 4294 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (19 chars, recommended min 30)
    The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (6.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (358 KB, recommended <100KB)
    The page weighs 358 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/usedebugvalue useDebugValue – React 200 749 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (21 chars, recommended min 30)
    The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (176 KB, recommended <100KB)
    The page weighs 176 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/usedeferredvalue useDeferredValue – React 200 2762 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (24 chars, recommended min 30)
    The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (5.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (296 KB, recommended <100KB)
    The page weighs 296 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/useeffect useEffect – React 200 7755 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (17 chars, recommended min 30)
    The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (587 KB, recommended <100KB)
    The page weighs 587 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/useeffectevent useEffectEvent – React 200 3095 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (5.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (303 KB, recommended <100KB)
    The page weighs 303 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/useid useId – React 200 1552 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (13 chars, recommended min 30)
    The title tag is only 13 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (235 KB, recommended <100KB)
    The page weighs 235 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/useinsertioneffect useInsertionEffect – React 200 1142 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (26 chars, recommended min 30)
    The title tag is only 26 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (4.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (182 KB, recommended <100KB)
    The page weighs 182 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/uselayouteffect useLayoutEffect – React 200 2119 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (5.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (256 KB, recommended <100KB)
    The page weighs 256 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/usememo useMemo – React 200 5836 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (15 chars, recommended min 30)
    The title tag is only 15 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (7.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (445 KB, recommended <100KB)
    The page weighs 445 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/useoptimistic useOptimistic – React 200 5038 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (21 chars, recommended min 30)
    The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (5.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (461 KB, recommended <100KB)
    The page weighs 461 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/usestate useState – React 200 4795 8 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (16 chars, recommended min 30)
    The title tag is only 16 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  7. Informational CONTENT: Very low text-to-HTML ratio (5.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  8. Informational PERFORMANCE: Large page (431 KB, recommended <100KB)
    The page weighs 431 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2023/03/16/introducing-react-dev Introducing react.dev – React 200 2893 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Informational META: Title too short (29 chars, recommended min 30)
    The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (6.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (222 KB, recommended <100KB)
    The page weighs 222 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2025/10/01/react-19-2 React 19.2 – React 200 2088 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 2 of 7 images missing alt text
    Some images are missing alt text (2 of 7 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  4. Recommended ACCESSIBILITY: 2 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (2 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Informational META: Title too short (18 chars, recommended min 30)
    The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (6.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (177 KB, recommended <100KB)
    The page weighs 177 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2026/02/24/the-react-foundation The React Foundation: A New Home for React... 200 422 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended META: Title too long (81 chars, recommended max 60)
    The title tag is 81 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results.
  3. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  4. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  5. Recommended ACCESSIBILITY: 4 of 5 images missing alt text
    Some images are missing alt text (4 of 5 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content.
  6. Recommended ACCESSIBILITY: 4 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (4 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  7. Informational CONTENT: Very low text-to-HTML ratio (3.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶community/team Meet the Team – React 200 1846 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended ACCESSIBILITY: 164 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (164 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (21 chars, recommended min 30)
    The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (2.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (397 KB, recommended <100KB)
    The page weighs 397 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn Quick Start – React 200 2771 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (19 chars, recommended min 30)
    The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (258 KB, recommended <100KB)
    The page weighs 258 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/conditional-rendering Conditional Rendering – React 200 2697 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (29 chars, recommended min 30)
    The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (283 KB, recommended <100KB)
    The page weighs 283 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/creating-a-react-app Creating a React App – React 200 1226 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (142 KB, recommended <100KB)
    The page weighs 142 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/describing-the-ui Describing the UI – React 200 2212 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (270 KB, recommended <100KB)
    The page weighs 270 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/editor-setup Editor Setup – React 200 774 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (20 chars, recommended min 30)
    The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (113 KB, recommended <100KB)
    The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/escape-hatches Escape Hatches – React 200 3801 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (336 KB, recommended <100KB)
    The page weighs 336 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/importing-and-exporting-components Importing and Exporting Components – React 200 1574 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (197 KB, recommended <100KB)
    The page weighs 197 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/keeping-components-pure Keeping Components Pure – React 200 2344 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (231 KB, recommended <100KB)
    The page weighs 231 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/managing-state Managing State – React 200 3120 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (301 KB, recommended <100KB)
    The page weighs 301 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/passing-props-to-a-component Passing Props to a Component – React 200 2329 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (260 KB, recommended <100KB)
    The page weighs 260 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/queueing-a-series-of-state-updates Queueing a Series of State Updates – React 200 2251 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (228 KB, recommended <100KB)
    The page weighs 228 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/react-compiler/incremental-adoption Incremental Adoption – React 200 1266 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (150 KB, recommended <100KB)
    The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/react-compiler/installation Installation – React 200 1326 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (20 chars, recommended min 30)
    The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (182 KB, recommended <100KB)
    The page weighs 182 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/react-compiler/introduction Introduction – React 200 1723 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (20 chars, recommended min 30)
    The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (6.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (162 KB, recommended <100KB)
    The page weighs 162 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/reacting-to-input-with-state Reacting to Input with State – React 200 3219 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 4 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (4 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (292 KB, recommended <100KB)
    The page weighs 292 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/referencing-values-with-refs Referencing Values with Refs – React 200 2588 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended ACCESSIBILITY: 1 images missing width/height (layout shift risk)
    Some images lack explicit dimensions (1 images missing width/height (layout shift risk)). If images aren't already sized via CSS, adding width and height attributes (or CSS aspect-ratio) helps prevent layout shifts during page load.
  5. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (248 KB, recommended <100KB)
    The page weighs 248 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/rendering-lists Rendering Lists – React 200 2466 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (265 KB, recommended <100KB)
    The page weighs 265 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/responding-to-events Responding to Events – React 200 3174 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (321 KB, recommended <100KB)
    The page weighs 321 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/typescript Using TypeScript – React 200 3111 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (24 chars, recommended min 30)
    The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (283 KB, recommended <100KB)
    The page weighs 283 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/your-first-component Your First Component – React 200 1738 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (198 KB, recommended <100KB)
    The page weighs 198 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react-compiler/configuration Configuration – React 200 628 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (21 chars, recommended min 30)
    The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (2.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (164 KB, recommended <100KB)
    The page weighs 164 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/usecontext useContext – React 200 2908 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (18 chars, recommended min 30)
    The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  6. Informational CONTENT: Very low text-to-HTML ratio (4.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (341 KB, recommended <100KB)
    The page weighs 341 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/useimperativehandle useImperativeHandle – React 200 1226 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (27 chars, recommended min 30)
    The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  6. Informational CONTENT: Very low text-to-HTML ratio (3.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (208 KB, recommended <100KB)
    The page weighs 208 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/usereducer useReducer – React 200 3730 7 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (18 chars, recommended min 30)
    The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational URL: Contains uppercase characters
    The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
  6. Informational CONTENT: Very low text-to-HTML ratio (5.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  7. Informational PERFORMANCE: Large page (357 KB, recommended <100KB)
    The page weighs 357 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2022/03/29/react-v18 React v18.0 – React 200 3968 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Informational META: Title too short (19 chars, recommended min 30)
    The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (8.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (266 KB, recommended <100KB)
    The page weighs 266 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2024/12/05/react-19 React v19 – React 200 5063 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Informational META: Title too short (17 chars, recommended min 30)
    The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (9.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (310 KB, recommended <100KB)
    The page weighs 310 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2025/10/07/react-compiler-1 React Compiler v1.0 – React 200 1886 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Informational META: Title too short (27 chars, recommended min 30)
    The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (7.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (161 KB, recommended <100KB)
    The page weighs 161 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components Denial of Service and Source Code Exposure in... 200 1283 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended META: Title too long (77 chars, recommended max 60)
    The title tag is 77 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results.
  3. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  4. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  5. Informational CONTENT: Very low text-to-HTML ratio (6.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (130 KB, recommended <100KB)
    The page weighs 130 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶community React Community – React 200 288 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended THIN CONTENT: Only 288 words
    This page has limited text content (288 words). Expanding the content could improve its relevance for search queries and provide more value to visitors.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (23 chars, recommended min 30)
    The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (2.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶community/docs-contributors Docs Contributors – React 200 273 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended THIN CONTENT: Only 273 words
    This page has limited text content (273 words). Expanding the content could improve its relevance for search queries and provide more value to visitors.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  6. Informational CONTENT: Very low text-to-HTML ratio (2.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶learn/add-react-to-an-existing-project Add React to an Existing Project – React 200 1389 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (156 KB, recommended <100KB)
    The page weighs 156 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/build-a-react-app-from-scratch Build a React app from Scratch – React 200 1930 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (7.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (157 KB, recommended <100KB)
    The page weighs 157 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/choosing-the-state-structure Choosing the State Structure – React 200 6065 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (498 KB, recommended <100KB)
    The page weighs 498 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/extracting-state-logic-into-a-reducer Extracting State Logic into a Reducer – React 200 3885 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (363 KB, recommended <100KB)
    The page weighs 363 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/installation Installation – React 200 604 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (20 chars, recommended min 30)
    The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (3.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (113 KB, recommended <100KB)
    The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/javascript-in-jsx-with-curly-braces JavaScript in JSX with Curly Braces – React 200 1567 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (3.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (218 KB, recommended <100KB)
    The page weighs 218 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/lifecycle-of-reactive-effects Lifecycle of Reactive Effects – React 200 6095 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (7.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (430 KB, recommended <100KB)
    The page weighs 430 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/manipulating-the-dom-with-refs Manipulating the DOM with Refs – React 200 4011 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (353 KB, recommended <100KB)
    The page weighs 353 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/passing-data-deeply-with-context Passing Data Deeply with Context – React 200 3835 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (345 KB, recommended <100KB)
    The page weighs 345 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/preserving-and-resetting-state Preserving and Resetting State – React 200 5077 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (474 KB, recommended <100KB)
    The page weighs 474 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/react-compiler React Compiler – React 200 431 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (103 KB, recommended <100KB)
    The page weighs 103 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/react-compiler/debugging Debugging and Troubleshooting – React 200 902 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (4.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (117 KB, recommended <100KB)
    The page weighs 117 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/removing-effect-dependencies Removing Effect Dependencies – React 200 7718 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (7.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (529 KB, recommended <100KB)
    The page weighs 529 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/reusing-logic-with-custom-hooks Reusing Logic with Custom Hooks – React 200 7486 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (6.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (595 KB, recommended <100KB)
    The page weighs 595 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/scaling-up-with-reducer-and-context Scaling Up with Reducer and Context – React 200 3060 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (293 KB, recommended <100KB)
    The page weighs 293 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/separating-events-from-effects Separating Events from Effects – React 200 5553 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (6.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (412 KB, recommended <100KB)
    The page weighs 412 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/sharing-state-between-components Sharing State Between Components – React 200 2460 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (233 KB, recommended <100KB)
    The page weighs 233 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/state-a-components-memory State: A Component's Memory – React 200 3987 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (6.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (338 KB, recommended <100KB)
    The page weighs 338 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/synchronizing-with-effects Synchronizing with Effects – React 200 7848 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (8.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (499 KB, recommended <100KB)
    The page weighs 499 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/understanding-your-ui-as-a-tree Understanding Your UI as a Tree – React 200 1538 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (163 KB, recommended <100KB)
    The page weighs 163 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/updating-arrays-in-state Updating Arrays in State – React 200 4487 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (394 KB, recommended <100KB)
    The page weighs 394 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/updating-objects-in-state Updating Objects in State – React 200 4058 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (5.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (355 KB, recommended <100KB)
    The page weighs 355 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/writing-markup-with-jsx Writing Markup with JSX – React 200 1599 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (4.7%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (189 KB, recommended <100KB)
    The page weighs 189 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/you-might-not-need-an-effect You Might Not Need an Effect – React 200 7437 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  5. Informational CONTENT: Very low text-to-HTML ratio (9.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (424 KB, recommended <100KB)
    The page weighs 424 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react-compiler/compiling-libraries Compiling Libraries – React 200 745 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (27 chars, recommended min 30)
    The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (3.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (170 KB, recommended <100KB)
    The page weighs 170 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react-compiler/directives Directives – React 200 970 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (18 chars, recommended min 30)
    The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (3.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (191 KB, recommended <100KB)
    The page weighs 191 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react-dom React DOM APIs – React 200 588 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (158 KB, recommended <100KB)
    The page weighs 158 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react-dom/client Client React DOM APIs – React 200 370 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (29 chars, recommended min 30)
    The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (138 KB, recommended <100KB)
    The page weighs 138 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react-dom/components React DOM Components – React 200 1097 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (323 KB, recommended <100KB)
    The page weighs 323 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react-dom/server Server React DOM APIs – React 200 464 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (29 chars, recommended min 30)
    The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.5%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (149 KB, recommended <100KB)
    The page weighs 149 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/apis Built-in React APIs – React 200 518 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (27 chars, recommended min 30)
    The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (149 KB, recommended <100KB)
    The page weighs 149 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/hooks Built-in React Hooks – React 200 1014 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (28 chars, recommended min 30)
    The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (3.9%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (173 KB, recommended <100KB)
    The page weighs 173 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/legacy Legacy React APIs – React 200 455 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (150 KB, recommended <100KB)
    The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶versions React Versions – React 200 1078 6 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (22 chars, recommended min 30)
    The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (3.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  6. Informational PERFORMANCE: Large page (228 KB, recommended <100KB)
    The page weighs 228 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog React Blog – React 200 1347 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Informational META: Title too short (18 chars, recommended min 30)
    The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  4. Informational CONTENT: Very low text-to-HTML ratio (7.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  5. Informational PERFORMANCE: Large page (104 KB, recommended <100KB)
    The page weighs 104 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2022/03/08/react-18-upgrade-guide How to Upgrade to React 18 – React 200 2837 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Informational CONTENT: Very low text-to-HTML ratio (9.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  5. Informational PERFORMANCE: Large page (177 KB, recommended <100KB)
    The page weighs 177 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2024/04/25/react-19-upgrade-guide React 19 Upgrade Guide – React 200 3863 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Informational CONTENT: Very low text-to-HTML ratio (7.0%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  5. Informational PERFORMANCE: Large page (320 KB, recommended <100KB)
    The page weighs 320 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2024/10/21/react-compiler-beta-release React Compiler Beta Release – React 200 1497 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended STRUCTURE: Heading hierarchy skips levels
    The heading structure skips levels (e.g., H1 directly to H3). Maintaining a logical hierarchy (H1 → H2 → H3) helps search engines understand content structure.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Informational CONTENT: Very low text-to-HTML ratio (7.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  5. Informational PERFORMANCE: Large page (124 KB, recommended <100KB)
    The page weighs 124 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2025/12/03/critical-security-vulnerability-in-react-server-components Critical Security Vulnerability in React... 200 1164 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended META: Title too long (66 chars, recommended max 60)
    The title tag is 66 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results.
  3. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  4. Informational CONTENT: Very low text-to-HTML ratio (5.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  5. Informational PERFORMANCE: Large page (129 KB, recommended <100KB)
    The page weighs 129 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2026/09/09/react-19-3 React 19.3 – React 200 4365 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Informational META: Title too short (18 chars, recommended min 30)
    The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  4. Informational CONTENT: Very low text-to-HTML ratio (6.4%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  5. Informational PERFORMANCE: Large page (374 KB, recommended <100KB)
    The page weighs 374 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶community/acknowledgements Acknowledgements – React 200 344 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (24 chars, recommended min 30)
    The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.2%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶community/translations Translations – React 200 457 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (20 chars, recommended min 30)
    The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.8%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶community/versioning-policy Versioning Policy – React 200 2331 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (25 chars, recommended min 30)
    The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational PERFORMANCE: Large page (131 KB, recommended <100KB)
    The page weighs 131 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶learn/setup Setup – React 200 405 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational META: Title too short (13 chars, recommended min 30)
    The title tag is only 13 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  5. Informational CONTENT: Very low text-to-HTML ratio (2.6%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
▶reference/react React Reference Overview – React 200 637 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational CONTENT: Very low text-to-HTML ratio (3.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  5. Informational PERFORMANCE: Large page (152 KB, recommended <100KB)
    The page weighs 152 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶reference/react/components Built-in React Components – React 200 359 5 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Recommended LINKS: 1 JavaScript-only links (not crawlable)
    Some links use JavaScript instead of standard URLs (1 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed.
  4. Informational CONTENT: Very low text-to-HTML ratio (2.1%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
  5. Informational PERFORMANCE: Large page (140 KB, recommended <100KB)
    The page weighs 140 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
▶blog/2021/06/08/the-plan-for-react-18 The Plan for React 18 – React 200 948 4 At Risk
  1. Pre-Launch Priority MISSING: Meta description
    Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
  2. Recommended MISSING: No structured data (JSON-LD)
    Adding JSON-LD structured data (schema markup) could enhance this page's search result appearance with rich snippets like star ratings or business info.
  3. Informational META: Title too short (29 chars, recommended min 30)
    The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
  4. Informational CONTENT: Very low text-to-HTML ratio (6.3%)
    This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
URL Migration Map

Shows how pages from legacy.reactjs.org (old docs, kept online) were mapped to pages on react.dev (new docs). Confidence scores indicate how certain the match is.

Old URL New URL Confidence Method Status SEO Changes Live Check
/ / 100% Exact Path Improved 5 fields Redirected
/blog/2022/03/08/react-18-upgrade-guide.html /blog/2022/03/08/react-18-upgrade-guide 100% Title Improved 3 fields Redirected
/docs/conditional-rendering.html /learn/conditional-rendering 100% Title Improved 3 fields Redirected, not the planned page
/docs/faq-versioning.html /community/versioning-policy 100% Title Improved 3 fields Redirected, not the planned page
/versions /versions 100% Exact Path Improved 6 fields Redirected, not the planned page
/blog/2017/04/07/react-v15.5.0.html /blog/2022/03/29/react-v18 83% Title Improved 5 fields Redirected, not the planned page
/docs/context.html /reference/react/usecontext 82% Title Improved 5 fields Redirected, not the planned page
/acknowledgements.html /community/acknowledgements 80% Title Improved 4 fields, 1 flag Redirected, not the planned page
/docs/react-component.html /reference/react-dom/components 80% Title Improved 5 fields, 1 flag Redirected, not the planned page
/docs/rendering-elements.html /learn/rendering-lists 78% Title Improved 5 fields Redirected, not the planned page
/docs/faq-functions.html /learn/passing-props-to-a-component 77% Title Improved 5 fields Redirected, not the planned page
/docs/refs-and-the-dom.html /learn/manipulating-the-dom-with-refs 66% Keyword Improved 5 fields Redirected, not the planned page
/blog/2017/09/08/dom-attributes-in-react-16.html /reference/react-dom 50% Keyword Improved 5 fields, 1 flag Redirected, not the planned page
/blog/2015/12/18/react-components-elements-and-instances.html /reference/react/components 40% Keyword Improved 5 fields, 1 flag Redirected, not the planned page
/blog (no match) 0% Origin Error Origin Error -- --
/blog/2016/02/19/new-versioning-scheme.html (no match) 0% Unmatched Missing -- Live redirect
/blog/2016/07/13/mixins-considered-harmful.html (no match) 0% Unmatched Missing -- Live redirect
/blog/2017/07/26/error-handling-in-react-16.html (no match) 0% Unmatched Missing -- Live redirect
/blog/2017/11/28/react-v16.2.0-fragment-support.html (no match) 0% Unmatched Missing -- Live redirect
/blog/2018/03/27/update-on-async-rendering.html (no match) 0% Unmatched Missing -- Live redirect
/blog/2018/06/07/you-probably-dont-need-derived-state.html (no match) 0% Unmatched Missing -- Live redirect
/blog/2018/09/10/introducing-the-react-profiler.html (no match) 0% Unmatched Missing -- Live redirect
/blog/2018/11/27/react-16-roadmap.html (no match) 0% Unmatched Missing -- Live redirect
/community/support.html (no match) 0% Unmatched Missing -- To parent section
/docs/accessibility.html (no match) 0% Unmatched Missing -- Live redirect
/docs/add-react-to-a-website.html (no match) 0% Unmatched Missing -- Live redirect
/docs/cdn-links.html (no match) 0% Unmatched Missing -- Live redirect
/docs/code-splitting.html (no match) 0% Unmatched Missing -- Live redirect
/docs/codebase-overview.html (no match) 0% Unmatched Missing -- Live redirect
/docs/components-and-props.html (no match) 0% Unmatched Missing -- Live redirect
/docs/composition-vs-inheritance.html (no match) 0% Unmatched Missing -- Live redirect
/docs/create-a-new-react-app.html (no match) 0% Unmatched Missing -- Live redirect
/docs/design-principles.html (no match) 0% Unmatched Missing -- Live redirect
/docs/dom-elements.html (no match) 0% Unmatched Missing -- Live redirect
/docs/error-boundaries.html (no match) 0% Unmatched Missing -- Live redirect
/docs/events.html (no match) 0% Unmatched Missing -- Live redirect
/docs/faq-ajax.html (no match) 0% Unmatched Missing -- Live redirect
/docs/faq-build.html (no match) 0% Unmatched Missing -- Live redirect
/docs/faq-internals.html (no match) 0% Unmatched Missing -- Live redirect
/docs/faq-state.html (no match) 0% Unmatched Missing -- Live redirect
/docs/faq-structure.html (no match) 0% Unmatched Missing -- Live redirect
/docs/faq-styling.html (no match) 0% Unmatched Missing -- Live redirect
/docs/forms.html (no match) 0% Unmatched Missing -- Live redirect
/docs/forwarding-refs.html (no match) 0% Unmatched Missing -- Live redirect
/docs/fragments.html (no match) 0% Unmatched Missing -- Live redirect
/docs/getting-started.html (no match) 0% Unmatched Missing -- Live redirect
/docs/glossary.html (no match) 0% Unmatched Missing -- Live redirect
/docs/handling-events.html (no match) 0% Unmatched Missing -- Live redirect
/docs/hello-world.html (no match) 0% Unmatched Missing -- Live redirect
/docs/higher-order-components.html (no match) 0% Unmatched Missing -- Live redirect
/docs/hooks-custom.html (no match) 0% Unmatched Missing -- Live redirect
/docs/hooks-effect.html (no match) 0% Unmatched Missing -- Live redirect
/docs/hooks-faq.html (no match) 0% Unmatched Missing -- Live redirect
/docs/hooks-intro.html (no match) 0% Unmatched Missing -- Live redirect
/docs/hooks-overview.html (no match) 0% Unmatched Missing -- Live redirect
/docs/hooks-reference.html (no match) 0% Unmatched Missing -- Live redirect
/docs/hooks-rules.html (no match) 0% Unmatched Missing -- Live redirect
/docs/hooks-state.html (no match) 0% Unmatched Missing -- Live redirect
/docs/how-to-contribute.html (no match) 0% Unmatched Missing -- Live redirect
/docs/implementation-notes.html (no match) 0% Unmatched Missing -- Live redirect
/docs/integrating-with-other-libraries.html (no match) 0% Unmatched Missing -- Live redirect
/docs/introducing-jsx.html (no match) 0% Unmatched Missing -- Live redirect
/docs/javascript-environment-requirements.html (no match) 0% Unmatched Missing -- Live redirect
/docs/jsx-in-depth.html (no match) 0% Unmatched Missing -- Live redirect
/docs/legacy-context.html (no match) 0% Unmatched Missing -- Live redirect
/docs/legacy-event-pooling.html (no match) 0% Unmatched Missing -- Live redirect
/docs/lifting-state-up.html (no match) 0% Unmatched Missing -- Live redirect
/docs/lists-and-keys.html (no match) 0% Unmatched Missing -- Live redirect
/docs/more-about-refs.html (no match) 0% Origin Error Origin Error -- --
/docs/optimizing-performance.html (no match) 0% Unmatched Missing -- Live redirect
/docs/portals.html (no match) 0% Unmatched Missing -- Live redirect
/docs/profiler.html (no match) 0% Unmatched Missing -- Live redirect
/docs/react-api.html (no match) 0% Unmatched Missing -- Live redirect
/docs/react-dom-client.html (no match) 0% Unmatched Missing -- Live redirect
/docs/react-dom-server.html (no match) 0% Unmatched Missing -- Live redirect
/docs/react-dom.html (no match) 0% Unmatched Missing -- Live redirect
/docs/react-without-es6.html (no match) 0% Unmatched Missing -- Live redirect
/docs/react-without-jsx.html (no match) 0% Unmatched Missing -- Live redirect
/docs/reconciliation.html (no match) 0% Unmatched Missing -- Live redirect
/docs/release-channels.html (no match) 0% Unmatched Missing -- Live redirect
/docs/render-props.html (no match) 0% Unmatched Missing -- Live redirect
/docs/state-and-lifecycle.html (no match) 0% Unmatched Missing -- Live redirect
/docs/static-type-checking.html (no match) 0% Unmatched Missing -- Live redirect
/docs/strict-mode.html (no match) 0% Unmatched Missing -- Live redirect
/docs/test-renderer.html (no match) 0% Unmatched Missing -- Live redirect
/docs/test-utils.html (no match) 0% Unmatched Missing -- Live redirect
/docs/testing-environments.html (no match) 0% Unmatched Missing -- Live redirect
/docs/testing-recipes.html (no match) 0% Unmatched Missing -- Live redirect
/docs/testing.html (no match) 0% Unmatched Missing -- Live redirect
/docs/thinking-in-react.html (no match) 0% Unmatched Missing -- Live redirect
/docs/typechecking-with-proptypes.html (no match) 0% Unmatched Missing -- Live redirect
/docs/uncontrolled-components.html (no match) 0% Unmatched Missing -- Live redirect
/docs/web-components.html (no match) 0% Unmatched Missing -- Live redirect
/docs/webcomponents.html (no match) 0% Origin Error Origin Error -- --
/languages (no match) 0% Unmatched Missing -- Live redirect
/redirect-to-codepen/reconciliation/index-used-as-key (no match) 0% Unmatched Missing -- Live redirect
/redirect-to-codepen/reconciliation/no-index-used-as-key (no match) 0% Unmatched Missing -- Live redirect
/redirect-to-codepen/uncontrolled-components/input-type-file (no match) 0% Unmatched Missing -- Live redirect
/tutorial/tutorial.html (no match) 0% Unmatched Missing -- Live redirect
/warnings/unknown-prop.html (no match) 0% Unmatched Missing -- Live redirect
-- /learn -- New Content New Content -- --
-- /reference/react -- New Content New Content -- --
-- /community -- New Content New Content -- --
-- /blog -- New Content New Content -- --
-- /community/translations -- New Content New Content -- --
-- /learn/add-react-to-an-existing-project -- New Content New Content -- --
-- /learn/creating-a-react-app -- New Content New Content -- --
-- /blog/2026/09/09/react-19-3 -- New Content New Content -- --
-- /blog/2026/02/24/the-react-foundation -- New Content New Content -- --
-- /blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components -- New Content New Content -- --
-- /blog/2025/12/03/critical-security-vulnerability-in-react-server-components -- New Content New Content -- --
-- /learn/installation -- New Content New Content -- --
-- /learn/describing-the-ui -- New Content New Content -- --
-- /learn/adding-interactivity -- New Content New Content -- --
-- /learn/managing-state -- New Content New Content -- --
-- /learn/escape-hatches -- New Content New Content -- --
-- /community/team -- New Content New Content -- --
-- /community/docs-contributors -- New Content New Content -- --
-- /learn/setup -- New Content New Content -- --
-- /learn/react-compiler -- New Content New Content -- --
-- /reference/react/apis -- New Content New Content -- --
-- /reference/react/legacy -- New Content New Content -- --
-- /reference/react-dom/client -- New Content New Content -- --
-- /reference/react-dom/server -- New Content New Content -- --
-- /reference/react-compiler/configuration -- New Content New Content -- --
-- /reference/react-compiler/directives -- New Content New Content -- --
-- /reference/react-compiler/compiling-libraries -- New Content New Content -- --
-- /blog/2023/03/16/introducing-react-dev -- New Content New Content -- --
-- /blog/2024/12/05/react-19 -- New Content New Content -- --
-- /blog/2024/04/25/react-19-upgrade-guide -- New Content New Content -- --
-- /blog/2024/10/21/react-compiler-beta-release -- New Content New Content -- --
-- /blog/2025/10/07/react-compiler-1 -- New Content New Content -- --
-- /blog/2025/10/01/react-19-2 -- New Content New Content -- --
-- /blog/2021/06/08/the-plan-for-react-18 -- New Content New Content -- --
-- /learn/tutorial-tic-tac-toe -- New Content New Content -- --
-- /learn/thinking-in-react -- New Content New Content -- --
-- /learn/build-a-react-app-from-scratch -- New Content New Content -- --
-- /learn/editor-setup -- New Content New Content -- --
-- /learn/typescript -- New Content New Content -- --
-- /learn/react-developer-tools -- New Content New Content -- --
-- /learn/react-compiler/introduction -- New Content New Content -- --
-- /learn/react-compiler/installation -- New Content New Content -- --
-- /learn/react-compiler/incremental-adoption -- New Content New Content -- --
-- /learn/react-compiler/debugging -- New Content New Content -- --
-- /learn/your-first-component -- New Content New Content -- --
-- /learn/importing-and-exporting-components -- New Content New Content -- --
-- /learn/writing-markup-with-jsx -- New Content New Content -- --
-- /learn/javascript-in-jsx-with-curly-braces -- New Content New Content -- --
-- /learn/keeping-components-pure -- New Content New Content -- --
-- /learn/understanding-your-ui-as-a-tree -- New Content New Content -- --
-- /learn/responding-to-events -- New Content New Content -- --
-- /learn/state-a-components-memory -- New Content New Content -- --
-- /learn/render-and-commit -- New Content New Content -- --
-- /learn/state-as-a-snapshot -- New Content New Content -- --
-- /learn/queueing-a-series-of-state-updates -- New Content New Content -- --
-- /learn/updating-objects-in-state -- New Content New Content -- --
-- /learn/updating-arrays-in-state -- New Content New Content -- --
-- /learn/reacting-to-input-with-state -- New Content New Content -- --
-- /learn/choosing-the-state-structure -- New Content New Content -- --
-- /learn/sharing-state-between-components -- New Content New Content -- --
-- /learn/preserving-and-resetting-state -- New Content New Content -- --
-- /learn/extracting-state-logic-into-a-reducer -- New Content New Content -- --
-- /learn/passing-data-deeply-with-context -- New Content New Content -- --
-- /learn/scaling-up-with-reducer-and-context -- New Content New Content -- --
-- /learn/referencing-values-with-refs -- New Content New Content -- --
-- /learn/synchronizing-with-effects -- New Content New Content -- --
-- /learn/you-might-not-need-an-effect -- New Content New Content -- --
-- /learn/lifecycle-of-reactive-effects -- New Content New Content -- --
-- /learn/separating-events-from-effects -- New Content New Content -- --
-- /learn/removing-effect-dependencies -- New Content New Content -- --
-- /learn/reusing-logic-with-custom-hooks -- New Content New Content -- --
-- /reference/react/usestate -- New Content New Content -- --
-- /reference/react/hooks -- New Content New Content -- --
-- /reference/react/useactionstate -- New Content New Content -- --
-- /reference/react/usecallback -- New Content New Content -- --
-- /reference/react/usedebugvalue -- New Content New Content -- --
-- /reference/react/usedeferredvalue -- New Content New Content -- --
-- /reference/react/useeffect -- New Content New Content -- --
-- /reference/react/useeffectevent -- New Content New Content -- --
-- /reference/react/useid -- New Content New Content -- --
-- /reference/react/useimperativehandle -- New Content New Content -- --
-- /reference/react/useinsertioneffect -- New Content New Content -- --
-- /reference/react/uselayouteffect -- New Content New Content -- --
-- /reference/react/usememo -- New Content New Content -- --
-- /reference/react/useoptimistic -- New Content New Content -- --
-- /reference/react/usereducer -- New Content New Content -- --
What changed on matched pages
Beforelegacy.reactjs.org (old docs, kept online) (crawled 2026-10-23_131318)
Afterreact.dev (new docs) (crawled 2026-10-23_131318)
11
Matched pairs compared
11
Pages with SEO changes
2
Red flags (0 priority, 2 recommended, 0 informational)
3
Low-confidence pairs hidden (matched below 70%)

Each old page is lined up with its new version and the parts search engines read are compared word by word. Flags describe what moved relative to the old page; they do not change the health counts on the Dashboard, and the Findings tab still describes the new site as it is. Old pages without a counterpart (83) are listed in Missing Pages.

Change matrix
Signal Kept Changed Added Lost Not comparable Coverage before -> after
Title 2 9 0 0 0 11 -> 11 present of 11
Meta description 0 0 1 0 0 0 -> 1 present of 11
H1 6 5 0 0 0 11 -> 11 present of 11
Section headings 1 9 1 0 0 10 -> 11 present of 11
Canonical 10 1 0 0 0 11 -> 11 present of 11
Indexability 10 1 0 0 0 10 -> 11 indexable of 11
Robots directives 0 0 0 0 0 0 -> 0 present of 11
Structured data 0 0 0 0 0 0 -> 0 present of 11
Social tags 0 11 0 0 0 11 -> 11 present of 11
hreflang 0 11 0 0 0 11 -> 11 present of 11
Language 11 0 0 0 0 11 -> 11 present of 11

Counts cover the 11 matched pairs at 70% confidence or more. Kept includes formatting-only differences (case, spacing, quotes); Not comparable means the data needed was not available on one side.

Red flags

Plus 2 flags on low-confidence pairs (hidden).

Matched pages

Click a row to see the Before | After card. Flagged pairs come first.

Old URL -> New URL Match Similarity Fields changed Flags
▶/blog/2015/12/18/react-components-elements-and-instances.html -> /reference/react/components/ 40% Keyword low confidence 19% 5 1 Recommended
https://legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.html -> https://react.dev/reference/react/components/
  • Recommended CHANGE: Word count dropped 86% (2,586 to 359)
    The new page carries much less text than the old one. Check that the main content made it across.
Title Changed40% similar
Before
React removed: Components, Elements, and Instances – Reactremoved: Blog
After
added: Built-in React added: Components – React

Words no longer in the title or the H1: blog, elements, instances.

H1 Changed48% similar
Before
React removed: Components, Elements, and Instances
After
added: Built-in React added: Components
Section headings Changed
Before
H2
  • removed: Managing the Instances
  • removed: Elements Describe the Tree
  • removed: Summary
  • removed: Further Reading
H3
  • removed: DOM Elements
  • removed: Component Elements
  • removed: Components Encapsulate Element Trees
  • removed: Components Can Be Classes or Functions
  • removed: Top-Down Reconciliation
After
H2
  • added: Built-in components
  • added: Your own components
H3
  • added: [email protected]
  • added: [email protected]
  • added: React Compiler
  • added: React DevTools
  • added: eslint-plugin-react-hooks
  • added: Rules of React
  • added: React Server Components
  • added: Legacy APIs

-9 / +10 headings. 1 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleReact removed: Components, Elements, and Instances – Reactremoved: Blog
og:titleadded: Built-in React added: Components – React
og:descriptionremoved: This blog site has been archived. Go to react.dev/blog to see the removed: recent posts. The difference between components, their instances, and removed: elements confuses many React beginners. Why are there three different terms to refer to something that is painted on screen? Managing the Instances If you’re new to React, you probably only worked with component classes and instances before. For example, you may declare a component by creating a class. When the app is running, you may have several instances of…
og:descriptionadded: The added: library for web and added: native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: az: az.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: en: /blog/2015/12/18/react-components-elements-and-instances.htmlremoved: es: es.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: fr: fr.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: hu: hu.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: it: it.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: ja: ja.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: ko: ko.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: mn: mn.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: pl: pl.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: pt-br: pt-br.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: ru: ru.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: tr: tr.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: uk: uk.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: x-default: /blog/2015/12/18/react-components-elements-and-instances.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.html
After
added: en: /reference/react/componentsadded: es: es.react.dev/reference/react/componentsadded: fr: fr.react.dev/reference/react/componentsadded: ja: ja.react.dev/reference/react/componentsadded: ko: ko.react.dev/reference/react/componentsadded: tr: tr.react.dev/reference/react/componentsadded: x-default: /reference/react/componentsadded: zh-hans: zh-hans.react.dev/reference/react/components
Kept: Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 2,586 -> 359 (-86%) Internal links: 36 -> 144 (+300%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/blog/2017/09/08/dom-attributes-in-react-16.html -> /reference/react-dom/ 50% Keyword low confidence 21% 5 1 Recommended
https://legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.html -> https://react.dev/reference/react-dom/
  • Recommended CHANGE: Word count dropped 56% (1,328 to 588)
    The new page carries much less text than the old one. Check that the main content made it across.
Title Changed30% similar
Before
DOM removed: Attributes in React 16 – Reactremoved: Blog
After
added: React DOM added: APIs – React

Words no longer in the title or the H1: 16, attributes, blog.

H1 Changed30% similar
Before
DOM removed: Attributes in React 16
After
added: React DOM added: APIs
Section headings Changed
Before
H2
  • removed: Why Are We Changing This?
  • removed: Should I Keep Data in Custom Attributes?
  • removed: Data and ARIA Attributes
  • removed: Migration Path
  • removed: Changes in Detail
  • removed: Try It!
  • removed: Thanks
  • removed: Future Work
H3 (none)
After
H2
  • added: APIs
  • added: Resource Preloading APIs
  • added: Server Rendering APIs
  • added: Entry points
  • added: Removed APIs
H3
  • added: [email protected]
  • added: [email protected]
  • added: React Compiler
  • added: React DevTools
  • added: eslint-plugin-react-hooks
  • added: Rules of React
  • added: React Server Components
  • added: Legacy APIs

-8 / +13 headings. 1 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleDOM removed: Attributes in React 16 – Reactremoved: Blog
og:titleadded: React DOM added: APIs – React
og:descriptionremoved: This blog site has been archived. Go to react.dev/blog to see the removed: recent posts. In the past, React used to ignore unknown DOM attributes. If you wrote JSX with an attribute that React doesn’t recognize, React would just skip it. removed: For removed: example, this: would render an empty div to the DOM with React 15: In React 16, we are making a change. Now, any unknown attributes will end up in the DOM: Why Are We Changing This? React has always provided a JavaScript-centric API to the DOM. Since React…
og:descriptionadded: The added: library added: for added: web and native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: az: az.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: en: /blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: es: es.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: fr: fr.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: hu: hu.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: it: it.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: ja: ja.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: ko: ko.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: mn: mn.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: pl: pl.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: pt-br: pt-br.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: ru: ru.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: tr: tr.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: uk: uk.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: x-default: /blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.html
After
added: en: /reference/react-domadded: es: es.react.dev/reference/react-domadded: fr: fr.react.dev/reference/react-domadded: ja: ja.react.dev/reference/react-domadded: ko: ko.react.dev/reference/react-domadded: tr: tr.react.dev/reference/react-domadded: x-default: /reference/react-domadded: zh-hans: zh-hans.react.dev/reference/react-dom
Kept: Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 1,328 -> 588 (-56%) Internal links: 28 -> 145 (+418%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/docs/react-component.html -> /reference/react-dom/components/ 80% Title 37% 5 1 Recommended
https://legacy.reactjs.org/docs/react-component.html -> https://react.dev/reference/react-dom/components/
  • Recommended CHANGE: Word count dropped 77% (4,808 to 1,097)
    The new page carries much less text than the old one. Check that the main content made it across.
Title Changed80% similar
Before
removed: React.Component – React
After
added: React DOM Components – React

Words no longer in the title or the H1: component.

H1 Changed80% similar
Before
removed: React.Component
After
added: React DOM Components
Section headings Changed
Before
H2
  • removed: Overview
  • removed: Reference
  • removed: Other APIs
  • removed: Class Properties
  • removed: Instance Properties
H3
  • removed: The Component Lifecycle
  • removed: Other APIs
  • removed: Class Properties
  • removed: Instance Properties
  • removed: Commonly Used Lifecycle Methods
  • removed: render()
  • removed: constructor()
  • removed: componentDidMount()
  • removed: componentDidUpdate()
  • removed: componentWillUnmount()
  • removed: Rarely Used Lifecycle Methods
  • removed: shouldComponentUpdate()
  • removed: static getDerivedStateFromProps()
  • removed: getSnapshotBeforeUpdate()
  • removed: Error boundaries
  • removed: static getDerivedStateFromError()
  • removed: componentDidCatch()
  • removed: Legacy Lifecycle Methods
  • removed: UNSAFE_componentWillMount()
  • removed: UNSAFE_componentWillReceiveProps()
  • removed: UNSAFE_componentWillUpdate()
  • removed: setState()
  • removed: forceUpdate()
  • removed: defaultProps
  • removed: displayName
  • removed: props
  • removed: state
After
H2
  • added: Common components
  • added: Form components
  • added: Resource and Metadata Components
  • added: All HTML components
  • added: All SVG components
H3
  • added: [email protected]
  • added: [email protected]
  • added: React Compiler
  • added: React DevTools
  • added: eslint-plugin-react-hooks
  • added: Rules of React
  • added: React Server Components
  • added: Legacy APIs
  • added: Custom HTML elements

-32 / +14 headings. 4 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleremoved: React.Component – React
og:titleadded: React DOM Components – React
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: The library for added: web and native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/docs/react-component.htmlremoved: az: az.legacy.reactjs.org/docs/react-component.htmlremoved: en: /docs/react-component.htmlremoved: es: es.legacy.reactjs.org/docs/react-component.htmlremoved: fr: fr.legacy.reactjs.org/docs/react-component.htmlremoved: hu: hu.legacy.reactjs.org/docs/react-component.htmlremoved: it: it.legacy.reactjs.org/docs/react-component.htmlremoved: ja: ja.legacy.reactjs.org/docs/react-component.htmlremoved: ko: ko.legacy.reactjs.org/docs/react-component.htmlremoved: mn: mn.legacy.reactjs.org/docs/react-component.htmlremoved: pl: pl.legacy.reactjs.org/docs/react-component.htmlremoved: pt-br: pt-br.legacy.reactjs.org/docs/react-component.htmlremoved: ru: ru.legacy.reactjs.org/docs/react-component.htmlremoved: tr: tr.legacy.reactjs.org/docs/react-component.htmlremoved: uk: uk.legacy.reactjs.org/docs/react-component.htmlremoved: x-default: /docs/react-component.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/docs/react-component.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/docs/react-component.html
After
added: en: /reference/react-dom/componentsadded: es: es.react.dev/reference/react-dom/componentsadded: fr: fr.react.dev/reference/react-dom/componentsadded: ja: ja.react.dev/reference/react-dom/componentsadded: ko: ko.react.dev/reference/react-dom/componentsadded: tr: tr.react.dev/reference/react-dom/componentsadded: x-default: /reference/react-dom/componentsadded: zh-hans: zh-hans.react.dev/reference/react-dom/components
Kept: Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 4,808 -> 1,097 (-77%) Internal links: 84 -> 143 (+70%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/acknowledgements.html -> /community/acknowledgements/ 80% Title 35% 4 1 Recommended
https://legacy.reactjs.org/acknowledgements.html -> https://react.dev/community/acknowledgements/
  • Recommended CHANGE: Word count dropped 85% (2,302 to 344)
    The new page carries much less text than the old one. Check that the main content made it across.
Title Changed80% similar
Before
Reactremoved: - Acknowledgements
After
added: Acknowledgements – React

Words no longer in the title or the H1: react.

Section headings Added
Before
H2 (none)
H3 (none)
After
H2
  • added: Past contributors
  • added: Additional Thanks
H3
  • added: GET INVOLVED

1 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleReactremoved: - Acknowledgements
og:titleadded: Acknowledgements – React
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: The library for added: web and native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/acknowledgements.htmlremoved: az: az.legacy.reactjs.org/acknowledgements.htmlremoved: en: /acknowledgements.htmlremoved: es: es.legacy.reactjs.org/acknowledgements.htmlremoved: fr: fr.legacy.reactjs.org/acknowledgements.htmlremoved: hu: hu.legacy.reactjs.org/acknowledgements.htmlremoved: it: it.legacy.reactjs.org/acknowledgements.htmlremoved: ja: ja.legacy.reactjs.org/acknowledgements.htmlremoved: ko: ko.legacy.reactjs.org/acknowledgements.htmlremoved: mn: mn.legacy.reactjs.org/acknowledgements.htmlremoved: pl: pl.legacy.reactjs.org/acknowledgements.htmlremoved: pt-br: pt-br.legacy.reactjs.org/acknowledgements.htmlremoved: ru: ru.legacy.reactjs.org/acknowledgements.htmlremoved: tr: tr.legacy.reactjs.org/acknowledgements.htmlremoved: uk: uk.legacy.reactjs.org/acknowledgements.htmlremoved: x-default: /acknowledgements.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/acknowledgements.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/acknowledgements.html
After
added: en: /community/acknowledgementsadded: es: es.react.dev/community/acknowledgementsadded: fr: fr.react.dev/community/acknowledgementsadded: ja: ja.react.dev/community/acknowledgementsadded: ko: ko.react.dev/community/acknowledgementsadded: tr: tr.react.dev/community/acknowledgementsadded: x-default: /community/acknowledgementsadded: zh-hans: zh-hans.react.dev/community/acknowledgements
Kept: H1, Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 2,302 -> 344 (-85%) Internal links: 16 -> 20 (+25%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/versions/ -> /versions/ 100% Exact Path 40% 6 Changed
https://legacy.reactjs.org/versions/ -> https://react.dev/versions/
Title Changed93% similar
Before
React removed: - removed: Versions
After
React added: Versions added: – added: React
Section headings Changed
Before
H2 (none)
H3
  • removed: 18.2.0
  • removed: 18.1.0
  • removed: 18.0.0
  • removed: 17.0.2
  • removed: 17.0.1
  • removed: 17.0.0
  • removed: 16.14.0
  • removed: 16.13.1
  • removed: 16.13.0
  • removed: 16.12.0
  • removed: 16.11
  • removed: 16.10.2
  • removed: 16.10.1
  • removed: 16.10
  • removed: 16.9
  • removed: 16.8
  • removed: 16.7
  • removed: 16.6
  • removed: 16.5
  • removed: 16.4
  • removed: 16.3
  • removed: 16.2
  • removed: 16.1
  • removed: 16.0
  • removed: 15.6
After
H2
  • added: Latest version: 19.3
  • added: Previous versions
  • added: Changelog
H3
  • added: REACT API
  • added: REACT DOM API
  • added: REACT COMPILER API
  • added: GET INVOLVED
  • added: STAY INFORMED
  • added: React 19
  • added: React 18
  • added: React 17
  • added: React 16
  • added: React 15
  • added: React 0.14
  • added: React 0.13
  • added: React 0.12
  • added: React 0.11
  • added: React 0.10 and below
  • added: Initial Commit

-25 / +19 headings. 4 template headings excluded.

Canonical Changed
Before
Points to another page: https://legacy.reactjs.org/versions/
After
Self-referencing: https://react.dev/versions

Now self-referencing (it pointed elsewhere before).

Indexability Changed
Before
Canonicalized to another URL
After
Indexable
Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleReact removed: - removed: Versions
og:titleReact added: Versions added: – added: React
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: The library for added: web and native user interfaces
hreflang Changed
Before
en: /versionsx-default: /versionsremoved: ar: ar.legacy.reactjs.org/versionsremoved: az: az.legacy.reactjs.org/versionsremoved: es: es.legacy.reactjs.org/versionsremoved: fr: fr.legacy.reactjs.org/versionsremoved: hu: hu.legacy.reactjs.org/versionsremoved: it: it.legacy.reactjs.org/versionsremoved: ja: ja.legacy.reactjs.org/versionsremoved: ko: ko.legacy.reactjs.org/versionsremoved: mn: mn.legacy.reactjs.org/versionsremoved: pl: pl.legacy.reactjs.org/versionsremoved: pt-br: pt-br.legacy.reactjs.org/versionsremoved: ru: ru.legacy.reactjs.org/versionsremoved: tr: tr.legacy.reactjs.org/versionsremoved: uk: uk.legacy.reactjs.org/versionsremoved: zh-hans: zh-hans.legacy.reactjs.org/versionsremoved: zh-hant: zh-hant.legacy.reactjs.org/versions
After
en: /versionsx-default: /versionsadded: es: es.react.dev/versionsadded: fr: fr.react.dev/versionsadded: ja: ja.react.dev/versionsadded: ko: ko.react.dev/versionsadded: tr: tr.react.dev/versionsadded: zh-hans: zh-hans.react.dev/versions
Kept: H1, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 172 -> 1,078 (+527%) Internal links: 17 -> 39 (+129%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/ -> / 100% Exact Path 12% 5 Changed
https://legacy.reactjs.org/ -> https://react.dev/
Title Changed16% similar
Before
Reactremoved: – A JavaScript library for building user interfaces
After
React

Words no longer in the title or the H1: building, interfaces, javascript, library, user.

Meta description Added
Before
(none)
After
added: React is the library for web and native user interfaces. Build user interfaces out of individual pieces called components written in JavaScript. React is designed to let you seamlessly combine components written by independent people, teams, and organizations.
Section headings Changed
Before
H2 (none)
H3
  • removed: Declarative
  • removed: Component-Based
  • removed: Learn Once, Write Anywhere
  • removed: A Simple Component
  • removed: A Stateful Component
  • removed: An Application
  • removed: A Component Using External Plugins
After
H2
  • added: Create user interfaces from components
  • added: Write components with code and markup
  • added: 3 Videos
  • added: Add interactivity wherever you need it
  • added: 5 Videos
  • added: Go full-stackwith a framework
  • added: 19 Videos
  • added: Use the best from every platform
  • added: Upgrade when the future is ready
  • added: React 19.3
  • added: The React Foundation: A New Home for React Hosted by the Linux Foundation
  • added: Additional Vulnerabilities in RSC
  • added: Vulnerability in React Server Components
  • added: Join a communityof millions
  • added: Welcome to theReact community
H3
  • added: Video.js
  • added: My video
  • added: VideoList.js
  • added: First video
  • added: Second video
  • added: Third video
  • added: SearchableVideoList.js
  • added: React: The Documentary
  • added: Rethinking Best Practices
  • added: Introducing React Native
  • added: Introducing React Hooks
  • added: Introducing Server Components
  • added: confs/[slug].js
  • added: React 18 Keynote
  • added: React 18 for App Developers
  • added: Streaming Server Rendering with Suspense
  • added: The First React Working Group
  • added: React Developer Tooling
  • added: React without memo
  • added: React Docs Keynote
  • added: Things I Learnt from the New React Docs
  • added: Learning in the Browser
  • added: The ROI of Designing with React
  • added: Interactive Playgrounds with React
  • added: Re-introducing Relay
  • added: React Native Desktop
  • added: On-device Machine Learning for React Native
  • added: React 18 for External Store Libraries
  • added: Building Accessible Components with React 18
  • added: Accessible Japanese Form Components with React
  • added: UI Tools for Artists
  • added: Hydrogen + React 18

-7 / +47 headings.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleReactremoved: – A JavaScript library for building user interfaces
og:titleReact
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: React is the library for added: web and native user interfaces. Build user interfacesadded: out of individual pieces called components written in JavaScript. React is designed to let you seamlessly combine components written by independent people, teams, and organizations.
hreflang Changed
Before
en: /x-default: /removed: ar: ar.legacy.reactjs.org/removed: az: az.legacy.reactjs.org/removed: es: es.legacy.reactjs.org/removed: fr: fr.legacy.reactjs.org/removed: hu: hu.legacy.reactjs.org/removed: it: it.legacy.reactjs.org/removed: ja: ja.legacy.reactjs.org/removed: ko: ko.legacy.reactjs.org/removed: mn: mn.legacy.reactjs.org/removed: pl: pl.legacy.reactjs.org/removed: pt-br: pt-br.legacy.reactjs.org/removed: ru: ru.legacy.reactjs.org/removed: tr: tr.legacy.reactjs.org/removed: uk: uk.legacy.reactjs.org/removed: zh-hans: zh-hans.legacy.reactjs.org/removed: zh-hant: zh-hant.legacy.reactjs.org/
After
en: /x-default: /added: es: es.react.dev/added: fr: fr.react.dev/added: ja: ja.react.dev/added: ko: ko.react.dev/added: tr: tr.react.dev/added: zh-hans: zh-hans.react.dev/
Kept: Canonical, Indexability, Language.
H1 kept: H1 count: 1 -> 2.
On neither page: Robots directives, Structured data.
Word count: 426 -> 1,436 (+237%) Internal links: 16 -> 22 (+38%) Images: 0 -> 37 (new) Images missing alt: 1 -> 24 (+2300%)
▶/blog/2017/04/07/react-v15.5.0.html -> /blog/2022/03/29/react-v18/ 83% Title 34% 5 Changed
https://legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.html -> https://react.dev/blog/2022/03/29/react-v18/
Title Changed54% similar
Before
React removed: v15.5.0 – Reactremoved: Blog
After
React added: v18.0 – React

Words no longer in the title or the H1: 5, blog.

H1 Changed83% similar
Before
React removed: v15.5.0
After
React added: v18.0
Section headings Changed
Before
H2
  • removed: Acknowledgements
  • removed: Installation
  • Changelog
  • removed: 15.5.0 (April 7, 2017)
H3
  • removed: New Deprecation Warnings
  • removed: Migrating from React.PropTypes
  • removed: Migrating from React.createClass
  • removed: Discontinuing support for React Addons
  • removed: React Test Utils
  • React
  • React DOM
  • removed: React Test Renderer
  • removed: React Addons
After
H2
  • added: What is Concurrent React?
  • added: Gradually Adopting Concurrent Features
  • added: Suspense in Data Frameworks
  • added: Server Components is Still in Development
  • added: What’s New in React 18
  • added: How to Upgrade
  • Changelog
H3
  • added: New Feature: Automatic Batching
  • added: New Feature: Transitions
  • added: New Suspense Features
  • added: New Client and Server Rendering APIs
  • added: New Strict Mode Behaviors
  • added: New Hooks
  • React
  • React DOM
  • added: React DOM Server
  • added: React DOM Test Utils
  • added: React Refresh
  • added: Server Components (Experimental)

-10 / +16 headings. 1 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleReact removed: v15.5.0 – Reactremoved: Blog
og:titleReact added: v18.0 – React
og:descriptionremoved: This blog site has been archived. Go to react.dev/blog to see the removed: recent posts. It’s been exactly one year since the last breaking change to React. Our next major release, React 16, will include some exciting improvements, including a complete rewrite of React’s internals. We take stability seriously, and removed: are committed to bringing those improvements to all of our users with minimal effort. To that end, today we’re releasing React 15.5.0. New Deprecation Warnings The biggest change is that we’ve…
og:descriptionadded: The added: library for web and added: native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: az: az.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: en: /blog/2017/04/07/react-v15.5.0.htmlremoved: es: es.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: fr: fr.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: hu: hu.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: it: it.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: ja: ja.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: ko: ko.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: mn: mn.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: pl: pl.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: pt-br: pt-br.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: ru: ru.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: tr: tr.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: uk: uk.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: x-default: /blog/2017/04/07/react-v15.5.0.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.html
After
added: en: /blog/2022/03/29/react-v18added: es: es.react.dev/blog/2022/03/29/react-v18added: fr: fr.react.dev/blog/2022/03/29/react-v18added: ja: ja.react.dev/blog/2022/03/29/react-v18added: ko: ko.react.dev/blog/2022/03/29/react-v18added: tr: tr.react.dev/blog/2022/03/29/react-v18added: x-default: /blog/2022/03/29/react-v18added: zh-hans: zh-hans.react.dev/blog/2022/03/29/react-v18
Kept: Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 1,616 -> 3,968 (+146%) Internal links: 30 -> 30 (same) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/docs/context.html -> /reference/react/useContext/ 82% Title 51% 5 Changed
https://legacy.reactjs.org/docs/context.html -> https://react.dev/reference/react/useContext/
Title Changed82% similar
Before
removed: Context – React
After
added: useContext – React

Words no longer in the title or the H1: context.

H1 Changed82% similar
Before
removed: Context
After
added: useContext
Section headings Changed
Before
H2
  • removed: When to Use Context
  • removed: Before You Use Context
  • removed: API
  • removed: Examples
  • removed: Caveats
  • removed: Legacy API
H3
  • removed: React.createContext
  • removed: Context.Provider
  • removed: Class.contextType
  • removed: Context.Consumer
  • removed: Context.displayName
  • removed: Dynamic Context
  • removed: Updating Context from a Nested Component
  • removed: Consuming Multiple Contexts
After
H2
  • added: Reference
  • added: Usage
  • added: Troubleshooting
H3
  • added: [email protected]
  • added: [email protected]
  • added: React Compiler
  • added: React DevTools
  • added: eslint-plugin-react-hooks
  • added: Rules of React
  • added: React Server Components
  • added: Legacy APIs
  • added: useContext(SomeContext)
  • added: Passing data deeply into the tree
  • added: Pitfall
  • added: Updating data passed via context
  • added: Specifying a fallback default value
  • added: Overriding context for a part of the tree
  • added: Optimizing re-renders when passing objects and functions
  • added: My component doesn’t see the value from my provider
  • added: I am always gettingundefinedfrom my context although the default value is different

-14 / +20 headings. 1 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleremoved: Context – React
og:titleadded: useContext – React
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: The library for added: web and native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/docs/context.htmlremoved: az: az.legacy.reactjs.org/docs/context.htmlremoved: en: /docs/context.htmlremoved: es: es.legacy.reactjs.org/docs/context.htmlremoved: fr: fr.legacy.reactjs.org/docs/context.htmlremoved: hu: hu.legacy.reactjs.org/docs/context.htmlremoved: it: it.legacy.reactjs.org/docs/context.htmlremoved: ja: ja.legacy.reactjs.org/docs/context.htmlremoved: ko: ko.legacy.reactjs.org/docs/context.htmlremoved: mn: mn.legacy.reactjs.org/docs/context.htmlremoved: pl: pl.legacy.reactjs.org/docs/context.htmlremoved: pt-br: pt-br.legacy.reactjs.org/docs/context.htmlremoved: ru: ru.legacy.reactjs.org/docs/context.htmlremoved: tr: tr.legacy.reactjs.org/docs/context.htmlremoved: uk: uk.legacy.reactjs.org/docs/context.htmlremoved: x-default: /docs/context.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/docs/context.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/docs/context.html
After
added: en: /reference/react/usecontextadded: es: es.react.dev/reference/react/usecontextadded: fr: fr.react.dev/reference/react/usecontextadded: ja: ja.react.dev/reference/react/usecontextadded: ko: ko.react.dev/reference/react/usecontextadded: tr: tr.react.dev/reference/react/usecontextadded: x-default: /reference/react/usecontextadded: zh-hans: zh-hans.react.dev/reference/react/usecontext
Kept: Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 3,262 -> 2,908 (-11%) Internal links: 82 -> 146 (+78%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/docs/faq-functions.html -> /learn/passing-props-to-a-component/ 77% Title 50% 5 Changed
https://legacy.reactjs.org/docs/faq-functions.html -> https://react.dev/learn/passing-props-to-a-component/
Title Changed78% similar
Before
Passing removed: Functions to removed: Components – React
After
Passing added: Props to added: a Component – React

Words no longer in the title or the H1: components, functions.

H1 Changed78% similar
Before
Passing removed: Functions to removed: Components
After
Passing added: Props to added: a Component
Section headings Changed
Before
H2 (none)
H3
  • removed: How do I pass an event handler (like onClick) to a component?
  • removed: How do I bind a function to a component instance?
  • removed: Is it OK to use arrow functions in render methods?
  • removed: Why is binding necessary at all?
  • removed: Why is my function being called every time the component renders?
  • removed: How do I pass a parameter to an event handler or callback?
  • removed: How can I prevent a function from being called too quickly or too many times in a row?
After
H2
  • added: Familiar props
  • added: Passing props to a component
  • added: Specifying a default value for a prop
  • added: Forwarding props with the JSX spread syntax
  • added: Passing JSX as children
  • added: How props change over time
  • added: Recap
  • added: Try out some challenges
H3
  • added: You will learn
  • added: Step 1: Pass props to the child component
  • added: Step 2: Read props inside the child component
  • added: Pitfall

-7 / +12 headings. 4 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titlePassing removed: Functions to removed: Components – React
og:titlePassing added: Props to added: a Component – React
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: The library for added: web and native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/docs/faq-functions.htmlremoved: az: az.legacy.reactjs.org/docs/faq-functions.htmlremoved: en: /docs/faq-functions.htmlremoved: es: es.legacy.reactjs.org/docs/faq-functions.htmlremoved: fr: fr.legacy.reactjs.org/docs/faq-functions.htmlremoved: hu: hu.legacy.reactjs.org/docs/faq-functions.htmlremoved: it: it.legacy.reactjs.org/docs/faq-functions.htmlremoved: ja: ja.legacy.reactjs.org/docs/faq-functions.htmlremoved: ko: ko.legacy.reactjs.org/docs/faq-functions.htmlremoved: mn: mn.legacy.reactjs.org/docs/faq-functions.htmlremoved: pl: pl.legacy.reactjs.org/docs/faq-functions.htmlremoved: pt-br: pt-br.legacy.reactjs.org/docs/faq-functions.htmlremoved: ru: ru.legacy.reactjs.org/docs/faq-functions.htmlremoved: tr: tr.legacy.reactjs.org/docs/faq-functions.htmlremoved: uk: uk.legacy.reactjs.org/docs/faq-functions.htmlremoved: x-default: /docs/faq-functions.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/docs/faq-functions.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/docs/faq-functions.html
After
added: en: /learn/passing-props-to-a-componentadded: es: es.react.dev/learn/passing-props-to-a-componentadded: fr: fr.react.dev/learn/passing-props-to-a-componentadded: ja: ja.react.dev/learn/passing-props-to-a-componentadded: ko: ko.react.dev/learn/passing-props-to-a-componentadded: tr: tr.react.dev/learn/passing-props-to-a-componentadded: x-default: /learn/passing-props-to-a-componentadded: zh-hans: zh-hans.react.dev/learn/passing-props-to-a-component
Kept: Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 2,189 -> 2,329 (about the same) Internal links: 81 -> 61 (-25%) Images: 0 -> 3 (new) Images missing alt: 1 -> 0 (-100%)
▶/docs/refs-and-the-dom.html -> /learn/manipulating-the-dom-with-refs/ 66% Keyword low confidence 28% 5 Changed
https://legacy.reactjs.org/docs/refs-and-the-dom.html -> https://react.dev/learn/manipulating-the-dom-with-refs/
Title Changed44% similar
Before
removed: Refs and the DOM – React
After
added: Manipulating the DOM added: with Refs – React
H1 Changed44% similar
Before
removed: Refs and the DOM
After
added: Manipulating the DOMadded: with Refs
Section headings Changed
Before
H2 (none)
H3
  • removed: When to Use Refs
  • removed: Don’t Overuse Refs
  • removed: Creating Refs
  • removed: Accessing Refs
  • removed: Exposing DOM Refs to Parent Components
  • removed: Callback Refs
  • removed: Legacy API: String Refs
  • removed: Caveats with callback refs
After
H2
  • added: Getting a ref to the node
  • added: Accessing another component’s DOM nodes
  • added: When React attaches the refs
  • added: Best practices for DOM manipulation with refs
  • added: Recap
  • added: Try out some challenges
H3
  • added: You will learn
  • added: Example: Focusing a text input
  • added: Example: Scrolling to an element
  • added: Pitfall

-8 / +10 headings. 4 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleremoved: Refs and the DOM – React
og:titleadded: Manipulating the DOM added: with Refs – React
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: The library for added: web and native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: az: az.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: en: /docs/refs-and-the-dom.htmlremoved: es: es.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: fr: fr.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: hu: hu.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: it: it.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: ja: ja.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: ko: ko.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: mn: mn.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: pl: pl.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: pt-br: pt-br.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: ru: ru.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: tr: tr.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: uk: uk.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: x-default: /docs/refs-and-the-dom.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/docs/refs-and-the-dom.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/docs/refs-and-the-dom.html
After
added: en: /learn/manipulating-the-dom-with-refsadded: es: es.react.dev/learn/manipulating-the-dom-with-refsadded: fr: fr.react.dev/learn/manipulating-the-dom-with-refsadded: ja: ja.react.dev/learn/manipulating-the-dom-with-refsadded: ko: ko.react.dev/learn/manipulating-the-dom-with-refsadded: tr: tr.react.dev/learn/manipulating-the-dom-with-refsadded: x-default: /learn/manipulating-the-dom-with-refsadded: zh-hans: zh-hans.react.dev/learn/manipulating-the-dom-with-refs
Kept: Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 2,171 -> 4,011 (+85%) Internal links: 81 -> 64 (-21%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/docs/rendering-elements.html -> /learn/rendering-lists/ 78% Title 39% 5 Changed
https://legacy.reactjs.org/docs/rendering-elements.html -> https://react.dev/learn/rendering-lists/
Title Changed79% similar
Before
Rendering removed: Elements – React
After
Rendering added: Lists – React

Words no longer in the title or the H1: elements.

H1 Changed79% similar
Before
Rendering removed: Elements
After
Rendering added: Lists
Section headings Changed
Before
H2
  • removed: Rendering an Element into the DOM
  • removed: Updating the Rendered Element
  • removed: React Only Updates What’s Necessary
H3 (none)
After
H2
  • added: Rendering data from arrays
  • added: Filtering arrays of items
  • added: Keeping list items in order withkey
  • added: Recap
  • added: Try out some challenges
H3
  • added: You will learn
  • added: Pitfall
  • added: Where to get yourkey
  • added: Rules of keys
  • added: Why does React need keys?
  • added: Pitfall

-3 / +11 headings. 4 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleRendering removed: Elements – React
og:titleRendering added: Lists – React
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: The library for added: web and native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/docs/rendering-elements.htmlremoved: az: az.legacy.reactjs.org/docs/rendering-elements.htmlremoved: en: /docs/rendering-elements.htmlremoved: es: es.legacy.reactjs.org/docs/rendering-elements.htmlremoved: fr: fr.legacy.reactjs.org/docs/rendering-elements.htmlremoved: hu: hu.legacy.reactjs.org/docs/rendering-elements.htmlremoved: it: it.legacy.reactjs.org/docs/rendering-elements.htmlremoved: ja: ja.legacy.reactjs.org/docs/rendering-elements.htmlremoved: ko: ko.legacy.reactjs.org/docs/rendering-elements.htmlremoved: mn: mn.legacy.reactjs.org/docs/rendering-elements.htmlremoved: pl: pl.legacy.reactjs.org/docs/rendering-elements.htmlremoved: pt-br: pt-br.legacy.reactjs.org/docs/rendering-elements.htmlremoved: ru: ru.legacy.reactjs.org/docs/rendering-elements.htmlremoved: tr: tr.legacy.reactjs.org/docs/rendering-elements.htmlremoved: uk: uk.legacy.reactjs.org/docs/rendering-elements.htmlremoved: x-default: /docs/rendering-elements.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/docs/rendering-elements.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/docs/rendering-elements.html
After
added: en: /learn/rendering-listsadded: es: es.react.dev/learn/rendering-listsadded: fr: fr.react.dev/learn/rendering-listsadded: ja: ja.react.dev/learn/rendering-listsadded: ko: ko.react.dev/learn/rendering-listsadded: tr: tr.react.dev/learn/rendering-listsadded: x-default: /learn/rendering-listsadded: zh-hans: zh-hans.react.dev/learn/rendering-lists
Kept: Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 875 -> 2,466 (+182%) Internal links: 81 -> 62 (-23%) Images: 1 -> 2 (+100%) Images missing alt: 1 -> 0 (-100%)
▶/blog/2022/03/08/react-18-upgrade-guide.html -> /blog/2022/03/08/react-18-upgrade-guide/ 100% Title 92% 3 Changed
https://legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html -> https://react.dev/blog/2022/03/08/react-18-upgrade-guide/
Title Changed80% similar
Before
How to Upgrade to React 18 – Reactremoved: Blog
After
How to Upgrade to React 18 – React

Words no longer in the title or the H1: blog.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:titleHow to Upgrade to React 18 – Reactremoved: Blog
og:titleHow to Upgrade to React 18 – React
og:descriptionremoved: This blog site has been archived. Go to react.dev/blog to see the removed: recent posts. As we shared in the release post, React 18 introduces features powered by our new concurrent renderer, with a gradual adoption strategy for removed: existing applications. In this post, we will guide you through the steps for upgrading to React 18. Please report any issues you encounter while upgrading to React 18. Note for React removed: Native removed: users: React 18 will ship in a future version of React Native. This is because React 1…
og:descriptionadded: The added: library for added: web and added: native added: user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: az: az.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: en: /blog/2022/03/08/react-18-upgrade-guide.htmlremoved: es: es.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: fr: fr.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: hu: hu.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: it: it.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: ja: ja.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: ko: ko.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: mn: mn.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: pl: pl.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: pt-br: pt-br.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: ru: ru.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: tr: tr.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: uk: uk.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: x-default: /blog/2022/03/08/react-18-upgrade-guide.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html
After
added: en: /blog/2022/03/08/react-18-upgrade-guideadded: es: es.react.dev/blog/2022/03/08/react-18-upgrade-guideadded: fr: fr.react.dev/blog/2022/03/08/react-18-upgrade-guideadded: ja: ja.react.dev/blog/2022/03/08/react-18-upgrade-guideadded: ko: ko.react.dev/blog/2022/03/08/react-18-upgrade-guideadded: tr: tr.react.dev/blog/2022/03/08/react-18-upgrade-guideadded: x-default: /blog/2022/03/08/react-18-upgrade-guideadded: zh-hans: zh-hans.react.dev/blog/2022/03/08/react-18-upgrade-guide
Kept: H1, Canonical, Indexability, Language.
Section headings kept: 3 template headings excluded.
On neither page: Meta description, Robots directives, Structured data.
Word count: 2,909 -> 2,837 (about the same) Internal links: 27 -> 18 (-33%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/docs/conditional-rendering.html -> /learn/conditional-rendering/ 100% Title 52% 3 Changed
https://legacy.reactjs.org/docs/conditional-rendering.html -> https://react.dev/learn/conditional-rendering/
Section headings Changed
Before
H2 (none)
H3
  • removed: Element Variables
  • removed: Inline If with Logical && Operator
  • removed: Inline If-Else with Conditional Operator
  • removed: Preventing Component from Rendering
After
H2
  • added: Conditionally returning JSX
  • added: Conditionally including JSX
  • added: Recap
  • added: Try out some challenges
H3
  • added: You will learn
  • added: Conditionally returning nothing withnull
  • added: Conditional (ternary) operator (? :)
  • added: Logical AND operator (&&)
  • added: Pitfall
  • added: Conditionally assigning JSX to a variable

-4 / +10 headings. 3 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: The library for added: web and native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: az: az.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: en: /docs/conditional-rendering.htmlremoved: es: es.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: fr: fr.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: hu: hu.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: it: it.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: ja: ja.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: ko: ko.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: mn: mn.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: pl: pl.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: pt-br: pt-br.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: ru: ru.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: tr: tr.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: uk: uk.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: x-default: /docs/conditional-rendering.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/docs/conditional-rendering.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/docs/conditional-rendering.html
After
added: en: /learn/conditional-renderingadded: es: es.react.dev/learn/conditional-renderingadded: fr: fr.react.dev/learn/conditional-renderingadded: ja: ja.react.dev/learn/conditional-renderingadded: ko: ko.react.dev/learn/conditional-renderingadded: tr: tr.react.dev/learn/conditional-renderingadded: x-default: /learn/conditional-renderingadded: zh-hans: zh-hans.react.dev/learn/conditional-rendering
Kept: Title, H1, Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 1,592 -> 2,697 (+69%) Internal links: 81 -> 61 (-25%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
▶/docs/faq-versioning.html -> /community/versioning-policy/ 100% Title 69% 3 Changed
https://legacy.reactjs.org/docs/faq-versioning.html -> https://react.dev/community/versioning-policy/
Section headings Changed
Before
H2 (none)
H3
  • Breaking Changes
  • Commitment to Stability
  • Gradual Upgrades via Warnings
  • What Counts as a Breaking Change?
  • If a Minor Release Includes No New Features, Why Isn’t It a Patch?
After
H2
  • added: Stable releases
  • added: All release channels
H3
  • added: GET INVOLVED
  • Breaking changes
  • Commitment to stability
  • Gradual upgrades via warnings
  • What counts as a breaking change?
  • If a minor release includes no new features, why isn’t it a patch?
  • added: Latest channel
  • added: Canary channel
  • added: Experimental channel

-0 / +6 headings. 2 template headings excluded.

Social tags Changed
Before
og:titleog:descriptionog:imageog:urlog:type
After
og:titleog:descriptionog:imageog:urlog:typeadded: twitter:cardadded: twitter:titleadded: twitter:descriptionadded: twitter:image
og:descriptionremoved: A JavaScript library for removed: building user interfaces
og:descriptionadded: The library for added: web and native user interfaces
hreflang Changed
Before
removed: ar: ar.legacy.reactjs.org/docs/faq-versioning.htmlremoved: az: az.legacy.reactjs.org/docs/faq-versioning.htmlremoved: en: /docs/faq-versioning.htmlremoved: es: es.legacy.reactjs.org/docs/faq-versioning.htmlremoved: fr: fr.legacy.reactjs.org/docs/faq-versioning.htmlremoved: hu: hu.legacy.reactjs.org/docs/faq-versioning.htmlremoved: it: it.legacy.reactjs.org/docs/faq-versioning.htmlremoved: ja: ja.legacy.reactjs.org/docs/faq-versioning.htmlremoved: ko: ko.legacy.reactjs.org/docs/faq-versioning.htmlremoved: mn: mn.legacy.reactjs.org/docs/faq-versioning.htmlremoved: pl: pl.legacy.reactjs.org/docs/faq-versioning.htmlremoved: pt-br: pt-br.legacy.reactjs.org/docs/faq-versioning.htmlremoved: ru: ru.legacy.reactjs.org/docs/faq-versioning.htmlremoved: tr: tr.legacy.reactjs.org/docs/faq-versioning.htmlremoved: uk: uk.legacy.reactjs.org/docs/faq-versioning.htmlremoved: x-default: /docs/faq-versioning.htmlremoved: zh-hans: zh-hans.legacy.reactjs.org/docs/faq-versioning.htmlremoved: zh-hant: zh-hant.legacy.reactjs.org/docs/faq-versioning.html
After
added: en: /community/versioning-policyadded: es: es.react.dev/community/versioning-policyadded: fr: fr.react.dev/community/versioning-policyadded: ja: ja.react.dev/community/versioning-policyadded: ko: ko.react.dev/community/versioning-policyadded: tr: tr.react.dev/community/versioning-policyadded: x-default: /community/versioning-policyadded: zh-hans: zh-hans.react.dev/community/versioning-policy
Kept: Title, H1, Canonical, Indexability, Language.
On neither page: Meta description, Robots directives, Structured data.
Word count: 1,247 -> 2,331 (+87%) Internal links: 82 -> 21 (-74%) Images: 0 -> 2 (new) Images missing alt: 1 -> 0 (-100%)
Pages Not Yet Rebuilt (83)

These pages from legacy.reactjs.org (old docs, kept online) were not found on react.dev (new docs). The migration team may want to consider rebuilding these pages or setting up redirects to the most relevant new page.

Old URL Title Words Original Health Live Today Suggested Fix
blog/2016/02/19/new-versioning-scheme.html New Versioning Scheme – React Blog 791 At Risk Redirected No action
blog/2016/07/13/mixins-considered-harmful.html Mixins Considered Harmful – React Blog 4881 At Risk Redirected No action
blog/2017/07/26/error-handling-in-react-16.html Error Handling in React 16 – React Blog 1140 At Risk Redirected No action
blog/2017/11/28/react-v16.2.0-fragment-support.html React v16.2.0: Improved Support for Fragments... 1776 At Risk Redirected No action
blog/2018/03/27/update-on-async-rendering.html Update on Async Rendering – React Blog 4329 At Risk Redirected No action
blog/2018/06/07/you-probably-dont-need-derived-state.html You Probably Don't Need Derived State – React Blog 3379 At Risk Redirected No action
blog/2018/09/10/introducing-the-react-profiler.html Introducing the React Profiler – React Blog 1398 At Risk Redirected No action
blog/2018/11/27/react-16-roadmap.html React 16.x Roadmap – React Blog 2958 At Risk Redirected No action
community/support.html (no title) 0 Needs Attention To parent section Choose a target and add a 301, or return 410 if it was retired on purpose
docs/accessibility.html Accessibility – React 3404 At Risk Redirected No action
docs/add-react-to-a-website.html (no title) 0 Needs Attention Redirected No action
docs/cdn-links.html CDN Links – React 484 At Risk Redirected No action
docs/code-splitting.html Code-Splitting – React 1976 At Risk Redirected No action
docs/codebase-overview.html Codebase Overview – React 1457 At Risk Redirected No action
docs/components-and-props.html Components and Props – React 1703 At Risk Redirected No action
docs/composition-vs-inheritance.html Composition vs Inheritance – React 1164 At Risk Redirected No action
docs/create-a-new-react-app.html (no title) 0 Needs Attention Redirected Point the old URL straight at https://react.dev/learn/creating-a-react-app
docs/design-principles.html Design Principles – React 3212 At Risk Redirected No action
docs/dom-elements.html DOM Elements – React 1740 At Risk Redirected No action
docs/error-boundaries.html Error Boundaries – React 1554 At Risk Redirected No action
docs/events.html SyntheticEvent – React 1541 At Risk Redirected No action
docs/faq-ajax.html AJAX and APIs – React 887 At Risk Redirected No action
docs/faq-build.html Babel, JSX, and Build Steps – React 370 At Risk Redirected No action
docs/faq-internals.html Virtual DOM and Internals – React 530 At Risk Redirected No action
docs/faq-state.html Component State – React 980 At Risk Redirected No action
docs/faq-structure.html File Structure – React 730 At Risk Redirected No action
docs/faq-styling.html Styling and CSS – React 517 At Risk Redirected No action
docs/forms.html Forms – React 2150 At Risk Redirected No action
docs/forwarding-refs.html Forwarding Refs – React 1620 At Risk Redirected No action
docs/fragments.html Fragments – React 837 At Risk Redirected No action
docs/getting-started.html (no title) 0 Needs Attention Redirected No action
docs/glossary.html Glossary of React Terms – React 1723 At Risk Redirected No action
docs/handling-events.html Handling Events – React 1215 At Risk Redirected No action
docs/hello-world.html Hello World – React 707 At Risk Redirected No action
docs/higher-order-components.html Higher-Order Components – React 3012 At Risk Redirected No action
docs/hooks-custom.html Building Your Own Hooks – React 2112 At Risk Redirected No action
docs/hooks-effect.html Using the Effect Hook – React 4198 At Risk Redirected No action
docs/hooks-faq.html Hooks FAQ – React 7730 At Risk Redirected No action
docs/hooks-intro.html Introducing Hooks – React 1806 At Risk Redirected No action
docs/hooks-overview.html Hooks at a Glance – React 2258 At Risk Redirected No action
docs/hooks-reference.html Hooks API Reference – React 5684 At Risk Redirected No action
docs/hooks-rules.html Rules of Hooks – React 1290 At Risk Redirected No action
docs/hooks-state.html Using the State Hook – React 2331 At Risk Redirected No action
docs/how-to-contribute.html How to Contribute – React 2042 At Risk Redirected No action
docs/implementation-notes.html Implementation Notes – React 5978 At Risk Redirected No action
docs/integrating-with-other-libraries.html Integrating with Other Libraries – React 3401 At Risk Redirected No action
docs/introducing-jsx.html Introducing JSX – React 1279 At Risk Redirected No action
docs/javascript-environment-requirements.html JavaScript Environment Requirements – React 374 At Risk Redirected No action
docs/jsx-in-depth.html JSX In Depth – React 2818 At Risk Redirected No action
docs/legacy-context.html Legacy Context – React 1428 At Risk Redirected No action
docs/legacy-event-pooling.html Event Pooling – React 457 At Risk Redirected No action
docs/lifting-state-up.html Lifting State Up – React 2706 At Risk Redirected No action
docs/lists-and-keys.html Lists and Keys – React 1876 At Risk Redirected No action
docs/optimizing-performance.html Optimizing Performance – React 2775 At Risk Redirected No action
docs/portals.html Portals – React 1186 At Risk Redirected No action
docs/profiler.html Profiler API – React 1052 At Risk Redirected No action
docs/react-api.html React Top-Level API – React 2824 At Risk Redirected No action
docs/react-dom-client.html ReactDOMClient – React 832 At Risk Redirected No action
docs/react-dom-server.html ReactDOMServer – React 1527 At Risk Redirected No action
docs/react-dom.html ReactDOM – React 1648 At Risk Redirected No action
docs/react-without-es6.html React Without ES6 – React 1364 At Risk Redirected No action
docs/react-without-jsx.html React Without JSX – React 636 At Risk Redirected No action
docs/reconciliation.html Reconciliation – React 1760 At Risk Redirected No action
docs/release-channels.html (no title) 0 Needs Attention Redirected No action
docs/render-props.html Render Props – React 2347 At Risk Redirected No action
docs/state-and-lifecycle.html State and Lifecycle – React 2622 At Risk Redirected No action
docs/static-type-checking.html Static Type Checking – React 2042 At Risk Redirected No action
docs/strict-mode.html Strict Mode – React 1996 At Risk Redirected No action
docs/test-renderer.html Test Renderer – React 1502 At Risk Redirected No action
docs/test-utils.html Test Utilities – React 1528 At Risk Redirected No action
docs/testing-environments.html Testing Environments – React 1125 At Risk Redirected No action
docs/testing-recipes.html Testing Recipes – React 3651 At Risk Redirected No action
docs/testing.html Testing Overview – React 665 At Risk Redirected No action
docs/thinking-in-react.html (no title) 0 Needs Attention Redirected No action
docs/typechecking-with-proptypes.html Typechecking With PropTypes – React 1551 At Risk Redirected No action
docs/uncontrolled-components.html Uncontrolled Components – React 1017 At Risk Redirected No action
docs/web-components.html Web Components – React 718 At Risk Redirected No action
languages React - Languages 255 At Risk Redirected No action
redirect-to-codepen/reconciliation/index-used-as-key 79 At Risk Redirected No action
redirect-to-codepen/reconciliation/no-index-used-as-key 79 At Risk Redirected No action
redirect-to-codepen/uncontrolled-components/input-type-file 79 At Risk Redirected No action
tutorial/tutorial.html (no title) 0 Needs Attention Redirected No action
warnings/unknown-prop.html Unknown Prop Warning – React 810 At Risk Redirected No action
What the old site's URLs do on the live site today

Webtrace requested 97 of 97 known old URLs on https://reactjs.org and followed every redirect step.

96 of 97
reach a live page (95 cleanly)
1
reach a parent section page, not their own
0
lost: homepage, soft 404, 404, 410 or loop
1
redirects to fix (temporary, chain, script or old copy)
14%
agree with the redirect plan (2 of 14)
82
missing in the crawl, resolving live today
0
not verified (blocked, robots.txt, client-rendered, errors, not checked)
Redirected: 96 To parent section: 1

Checked live on 2026-10-23 18:23 UTC as WebtraceBot; results are point-in-time. Blocked, robots.txt, client-rendered, errors and unchecked URLs are left out of the counts. Display only: the migration health label and counts are not changed by this check.

Fix list (2)

Worst first (red, then amber, then not verified), then by estimated importance.

# Old URL Today Hops Lands on Suggested target Importance Action Changed (approx.)
1 /community/support.html To parent sectionAnother host 308 -> 200 https://react.dev/community
React Community – React
 -- 50 Choose a target and add a 301, or return 410 if it was retired on purpose between 2023-03-06 and 2023-04-02 (became 301) (approx.) last 200 first change
2 /docs/create-a-new-react-app.html RedirectedChainAnother host 308 -> 308 -> 200 https://react.dev/learn/creating-a-react-app
Creating a React App – React
 https://react.dev/learn/creating-a-react-app 48 Point the old URL straight at https://react.dev/learn/creating-a-react-app --
Verified redirect fixes

The fixes CSV lists every old URL above that needs attention. The .htaccess file holds 1 permanent (301) rewrite rules for the old URLs that have a suggested target, grouped by the host they belong on; the others are listed as comments. Review every rule before installing it, then run the check again.

Download fixes (CSV) Download rules (.htaccess)
Preview the .htaccess rules 
# Redirect fixes for old URLs - Generated by Webtrace 0.4.0
# From the live Old URL check of 2026-10-23 (UTC). Results are point-in-time:
# review every rule, install each block on the host its header names, then re-check.
# Rules are written for a per-directory (.htaccess) context and send a 301.

RewriteEngine On

# --- Install on reactjs.org ---
# /docs/create-a-new-react-app.html -> https://react.dev/learn/creating-a-react-app (Redirected; live: 308 -> 308 -> 200)
RewriteRule ^docs/create-a-new-react-app\.html$ https://react.dev/learn/creating-a-react-app [R=301,L]

# --- Old URLs without a suggested target (choose one, or return 410 if retired) ---
# /community/support.html (To parent section): Choose a target and add a 301, or return 410 if it was retired on purpose
When old URLs changed (approx.)

For 1 old URL that no longer reaches its own page (lost, or sent to a parent section), the quarter of the first Internet Archive capture after the page's last 200 answer: moved (a redirect) or gone (an error). Archive captures are samples, so dates are approximate.

Moved (3xx): 1 Gone (4xx/5xx): 0
When old URLs changed Stacked bars per quarter: 1 old URLs moved and 0 were gone at their first archive capture after the last 200 answer. 0 1 Q2 2023: 1 moved (3xx), 0 gone (4xx/5xx) Q2 2023
Show the chart as a table
PeriodMoved (3xx)Gone (4xx/5xx)
Q2 202310
Lost by section
SectionCheckedReach their pageReach a parent pageLostNot verified
/community/10100
/docs/7575000
/blog/1212000
/44000
/redirect-to-codepen/33000
/tutorial/11000
/warnings/11000
Every checked old URL (97)
Old URLTodayHopsLands onMatches planImportance
/docs/accessibility.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/accessibility.html -- 60
/docs/faq-ajax.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/faq-ajax.html -- 60
/docs/hello-world.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/hello-world.html -- 60
/docs/hooks-intro.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/hooks-intro.html -- 60
/docs/how-to-contribute.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/how-to-contribute.html -- 60
/docs/react-api.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/react-api.html -- 60
/docs/testing.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/testing.html -- 60
/docs/cdn-links.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/cdn-links.html -- 58
/docs/code-splitting.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/code-splitting.html -- 58
/docs/codebase-overview.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/codebase-overview.html -- 58
/docs/components-and-props.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/components-and-props.html -- 58
/docs/composition-vs-inheritance.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/composition-vs-inheritance.html -- 58
/docs/design-principles.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/design-principles.html -- 58
/docs/dom-elements.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/dom-elements.html -- 58
/docs/error-boundaries.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/error-boundaries.html -- 58
/docs/events.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/events.html -- 58
/docs/faq-build.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/faq-build.html -- 58
/docs/faq-internals.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/faq-internals.html -- 58
/docs/faq-state.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/faq-state.html -- 58
/docs/faq-structure.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/faq-structure.html -- 58
/docs/faq-styling.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/faq-styling.html -- 58
/docs/forms.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/forms.html -- 58
/docs/forwarding-refs.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/forwarding-refs.html -- 58
/docs/fragments.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/fragments.html -- 58
/docs/glossary.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/glossary.html -- 58
/docs/handling-events.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/handling-events.html -- 58
/docs/higher-order-components.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/higher-order-components.html -- 58
/docs/hooks-custom.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/hooks-custom.html -- 58
/docs/hooks-effect.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/hooks-effect.html -- 58
/docs/hooks-faq.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/hooks-faq.html -- 58
/docs/hooks-overview.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/hooks-overview.html -- 58
/docs/hooks-reference.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/hooks-reference.html -- 58
/docs/hooks-rules.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/hooks-rules.html -- 58
/docs/hooks-state.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/hooks-state.html -- 58
/docs/implementation-notes.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/implementation-notes.html -- 58
/docs/integrating-with-other-libraries.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/integrating-with-other-libraries.html -- 58
/docs/introducing-jsx.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/introducing-jsx.html -- 58
/docs/javascript-environment-requirements.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/javascript-environment-requirements.html -- 58
/docs/jsx-in-depth.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/jsx-in-depth.html -- 58
/docs/lifting-state-up.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/lifting-state-up.html -- 58
/docs/lists-and-keys.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/lists-and-keys.html -- 58
/docs/optimizing-performance.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/optimizing-performance.html -- 58
/docs/portals.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/portals.html -- 58
/docs/profiler.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/profiler.html -- 58
/docs/react-dom-client.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/react-dom-client.html -- 58
/docs/react-dom-server.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/react-dom-server.html -- 58
/docs/react-dom.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/react-dom.html -- 58
/docs/react-without-es6.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/react-without-es6.html -- 58
/docs/react-without-jsx.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/react-without-jsx.html -- 58
/docs/reconciliation.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/reconciliation.html -- 58
/docs/render-props.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/render-props.html -- 58
/docs/state-and-lifecycle.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/state-and-lifecycle.html -- 58
/docs/static-type-checking.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/static-type-checking.html -- 58
/docs/strict-mode.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/strict-mode.html -- 58
/docs/test-renderer.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/test-renderer.html -- 58
/docs/test-utils.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/test-utils.html -- 58
/docs/testing-environments.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/testing-environments.html -- 58
/docs/testing-recipes.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/testing-recipes.html -- 58
/docs/typechecking-with-proptypes.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/typechecking-with-proptypes.html -- 58
/docs/uncontrolled-components.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/uncontrolled-components.html -- 58
/docs/web-components.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/web-components.html -- 58
/languages/ RedirectedAnother hostLands on the kept old site 308 -> 308 -> 200 https://legacy.reactjs.org/languages -- 55
/community/support.html To parent sectionAnother host 308 -> 200 https://react.dev/community -- 50
/docs/getting-started.html RedirectedAnother host 308 -> 200 https://react.dev/learn -- 50
/tutorial/tutorial.html RedirectedAnother host 308 -> 200 https://react.dev/learn/tutorial-tic-tac-toe -- 50
/docs/add-react-to-a-website.html RedirectedAnother host 308 -> 200 https://react.dev/learn/add-react-to-an-existing-project -- 48
/docs/create-a-new-react-app.html RedirectedChainAnother host 308 -> 308 -> 200 https://react.dev/learn/creating-a-react-app -- 48
/docs/release-channels.html RedirectedAnother host 308 -> 200 https://react.dev/community/versioning-policy -- 48
/docs/thinking-in-react.html RedirectedAnother host 308 -> 200 https://react.dev/learn/thinking-in-react -- 48
/docs/legacy-context.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/legacy-context.html -- 30
/warnings/unknown-prop.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/warnings/unknown-prop.html -- 30
/blog/2018/03/27/update-on-async-rendering.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2018/03/27/update-on-async-rendering.html -- 26
/docs/legacy-event-pooling.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/legacy-event-pooling.html -- 26
/blog/2016/07/13/mixins-considered-harmful.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2016/07/13/mixins-considered-harmful.html -- 24
/blog/2018/06/07/you-probably-dont-need-derived-state.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2018/06/07/you-probably-dont-need-derived-state.html -- 22
/blog/2016/02/19/new-versioning-scheme.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2016/02/19/new-versioning-scheme.html -- 20
/blog/2017/07/26/error-handling-in-react-16.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2017/07/26/error-handling-in-react-16.html -- 20
/blog/2017/11/28/react-v16.2.0-fragment-support.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2017/11/28/react-v16.2.0-fragment-support.html -- 16
/blog/2018/09/10/introducing-the-react-profiler.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2018/09/10/introducing-the-react-profiler.html -- 16
/blog/2018/11/27/react-16-roadmap.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2018/11/27/react-16-roadmap.html -- 16
/redirect-to-codepen/reconciliation/index-used-as-key RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/redirect-to-codepen/reconciliation/index-used-as-key -- 11
/redirect-to-codepen/reconciliation/no-index-used-as-key RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/redirect-to-codepen/reconciliation/no-index-used-as-key -- 11
/redirect-to-codepen/uncontrolled-components/input-type-file RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/redirect-to-codepen/uncontrolled-components/input-type-file -- 11
/ RedirectedAnother host 308 -> 200 https://react.dev/ Yes 65
/acknowledgements.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/acknowledgements.html No -- live: https://legacy.reactjs.org/acknowledgements.html; plan: https://react.dev/community/acknowledgements/ 65
/docs/conditional-rendering.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/conditional-rendering.html No -- live: https://legacy.reactjs.org/docs/conditional-rendering.html; plan: https://react.dev/learn/conditional-rendering/ 58
/docs/context.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/context.html No -- live: https://legacy.reactjs.org/docs/context.html; plan: https://react.dev/reference/react/useContext/ 58
/docs/faq-functions.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/faq-functions.html No -- live: https://legacy.reactjs.org/docs/faq-functions.html; plan: https://react.dev/learn/passing-props-to-a-component/ 58
/docs/faq-versioning.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/faq-versioning.html No -- live: https://legacy.reactjs.org/docs/faq-versioning.html; plan: https://react.dev/community/versioning-policy/ 58
/docs/react-component.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/react-component.html No -- live: https://legacy.reactjs.org/docs/react-component.html; plan: https://react.dev/reference/react-dom/components/ 58
/docs/refs-and-the-dom.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/refs-and-the-dom.html No -- live: https://legacy.reactjs.org/docs/refs-and-the-dom.html; plan: https://react.dev/learn/manipulating-the-dom-with-refs/ 58
/docs/rendering-elements.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/docs/rendering-elements.html No -- live: https://legacy.reactjs.org/docs/rendering-elements.html; plan: https://react.dev/learn/rendering-lists/ 58
/versions/ RedirectedAnother hostLands on the kept old site 308 -> 308 -> 200 https://legacy.reactjs.org/versions No -- live: https://legacy.reactjs.org/versions; plan: https://react.dev/versions/ 55
/blog/2022/03/08/react-18-upgrade-guide.html RedirectedAnother host 308 -> 200 https://react.dev/blog/2022/03/08/react-18-upgrade-guide Yes 33
/blog/2015/12/18/react-components-elements-and-instances.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.html No -- live: https://legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.html; plan: https://react.dev/reference/react/components/ 20
/blog/2017/04/07/react-v15.5.0.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.html No -- live: https://legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.html; plan: https://react.dev/blog/2022/03/29/react-v18/ 20
/blog/2017/09/08/dom-attributes-in-react-16.html RedirectedAnother hostLands on the kept old site 308 -> 200 https://legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.html No -- live: https://legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.html; plan: https://react.dev/reference/react-dom/ 16
About this check
  • Results are point-in-time: a server can change its redirects at any moment.
  • Requests identify as WebtraceBot; bot-specific or location-based redirects may differ for people.
  • Script (JavaScript) redirects are only flagged, never followed.
  • Soft-404 wording is recognized in English only.
  • Importance is an internal estimate from the old site's own links, sitemap, depth and size, not a count of backlinks.
  • Dates of change come from Internet Archive captures and are approximate.
Sections: Site-Wide Achievements Site-Wide Findings Pre-Launch Priority (99) Recommended (283) Informational (272) Implemented Well
Site-Wide Site-Wide Achievements (4) ▲ Sections

Cross-page analysis confirms these site-wide SEO strengths.

site-wide 100% HTTPS internal links -- 100%
All internal links use HTTPS, ensuring a consistent secure experience.
site-wide No orphan pages -- All linked
Every page has at least one inbound internal link.
site-wide Fast average response time -- 102ms
The site's average server response time is excellent.
site-wide Strong average content depth -- 2687 words avg
The site maintains substantial content across pages.
Site-Wide Site-Wide Findings (2) ▲ Sections

Cross-page analysis identified these site-wide patterns worth reviewing.

Finding Recommendation
Recommended SITE: 2 pages share duplicate title "Installation – React"
▶ 2 affected pages
Site-wide observation: 2 pages share duplicate title "Installation – React".
Recommended SITE: 2 pages share duplicate H1 "Installation"
▶ 2 affected pages
Site-wide observation: 2 pages share duplicate H1 "Installation".
Pre-Launch Priority Pre-Launch Priority (99 findings across 99 pages) ▲ Sections
blog (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2021/06/08/the-plan-for-react-18 (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2022/03/08/react-18-upgrade-guide (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2022/03/29/react-v18 (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2023/03/16/introducing-react-dev (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2024/04/25/react-19-upgrade-guide (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2024/10/21/react-compiler-beta-release (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2024/12/05/react-19 (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2025/10/01/react-19-2 (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2025/10/07/react-compiler-1 (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2025/12/03/critical-security-vulnerability-in-react-server-components (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2026/02/24/the-react-foundation (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
blog/2026/09/09/react-19-3 (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
community (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
community/acknowledgements (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
community/docs-contributors (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
community/team (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
community/translations (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
community/versioning-policy (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/add-react-to-an-existing-project (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/adding-interactivity (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/build-a-react-app-from-scratch (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/choosing-the-state-structure (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/conditional-rendering (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/creating-a-react-app (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/describing-the-ui (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/editor-setup (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/escape-hatches (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/extracting-state-logic-into-a-reducer (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/importing-and-exporting-components (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/installation (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/javascript-in-jsx-with-curly-braces (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/keeping-components-pure (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/lifecycle-of-reactive-effects (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/managing-state (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/manipulating-the-dom-with-refs (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/passing-data-deeply-with-context (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/passing-props-to-a-component (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/preserving-and-resetting-state (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/queueing-a-series-of-state-updates (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/react-compiler (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/react-compiler/debugging (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/react-compiler/incremental-adoption (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/react-compiler/installation (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/react-compiler/introduction (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/react-developer-tools (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/reacting-to-input-with-state (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/referencing-values-with-refs (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/removing-effect-dependencies (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/render-and-commit (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/rendering-lists (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/responding-to-events (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/reusing-logic-with-custom-hooks (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/scaling-up-with-reducer-and-context (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/separating-events-from-effects (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/setup (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/sharing-state-between-components (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/state-a-components-memory (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/state-as-a-snapshot (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/synchronizing-with-effects (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/thinking-in-react (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/tutorial-tic-tac-toe (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/typescript (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/understanding-your-ui-as-a-tree (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/updating-arrays-in-state (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/updating-objects-in-state (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/writing-markup-with-jsx (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/you-might-not-need-an-effect (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
learn/your-first-component (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react-compiler/compiling-libraries (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react-compiler/configuration (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react-compiler/directives (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react-dom (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react-dom/client (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react-dom/components (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react-dom/server (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/apis (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/components (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/hooks (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/legacy (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/useactionstate (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/usecallback (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/usecontext (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/usedebugvalue (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/usedeferredvalue (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/useeffect (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/useeffectevent (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/useid (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/useimperativehandle (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/useinsertioneffect (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/uselayouteffect (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/usememo (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/useoptimistic (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/usereducer (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
reference/react/usestate (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
versions (1 findings)
▶
Finding Recommendation
MISSING: Meta description Adding a meta description would strengthen this page's search snippet and give users a better preview of what they'll find.
Informational Informational (272 findings across 100 pages) ▲ Sections
/ (4 findings)
▶
Finding Recommendation
META: Title too short (5 chars, recommended min 30) The title tag is only 5 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
MULTIPLE H1: 2 H1 tags found This page has more than one H1 heading. While not critical, using a single H1 helps search engines understand the page's primary topic more clearly.
CONTENT: Very low text-to-HTML ratio (3.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (266 KB, recommended <100KB) The page weighs 266 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/useactionstate (4 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (6.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (475 KB, recommended <100KB) The page weighs 475 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/usecallback (4 findings)
▶
Finding Recommendation
META: Title too short (19 chars, recommended min 30) The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (6.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (358 KB, recommended <100KB) The page weighs 358 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/usecontext (4 findings)
▶
Finding Recommendation
META: Title too short (18 chars, recommended min 30) The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (4.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (341 KB, recommended <100KB) The page weighs 341 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/usedebugvalue (4 findings)
▶
Finding Recommendation
META: Title too short (21 chars, recommended min 30) The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (3.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (176 KB, recommended <100KB) The page weighs 176 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/usedeferredvalue (4 findings)
▶
Finding Recommendation
META: Title too short (24 chars, recommended min 30) The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (5.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (296 KB, recommended <100KB) The page weighs 296 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/useeffect (4 findings)
▶
Finding Recommendation
META: Title too short (17 chars, recommended min 30) The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (7.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (587 KB, recommended <100KB) The page weighs 587 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/useeffectevent (4 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (5.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (303 KB, recommended <100KB) The page weighs 303 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/useid (4 findings)
▶
Finding Recommendation
META: Title too short (13 chars, recommended min 30) The title tag is only 13 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (3.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (235 KB, recommended <100KB) The page weighs 235 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/useimperativehandle (4 findings)
▶
Finding Recommendation
META: Title too short (27 chars, recommended min 30) The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (3.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (208 KB, recommended <100KB) The page weighs 208 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/useinsertioneffect (4 findings)
▶
Finding Recommendation
META: Title too short (26 chars, recommended min 30) The title tag is only 26 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (4.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (182 KB, recommended <100KB) The page weighs 182 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/uselayouteffect (4 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (5.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (256 KB, recommended <100KB) The page weighs 256 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/usememo (4 findings)
▶
Finding Recommendation
META: Title too short (15 chars, recommended min 30) The title tag is only 15 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (7.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (445 KB, recommended <100KB) The page weighs 445 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/useoptimistic (4 findings)
▶
Finding Recommendation
META: Title too short (21 chars, recommended min 30) The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (5.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (461 KB, recommended <100KB) The page weighs 461 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/usereducer (4 findings)
▶
Finding Recommendation
META: Title too short (18 chars, recommended min 30) The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (5.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (357 KB, recommended <100KB) The page weighs 357 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/usestate (4 findings)
▶
Finding Recommendation
META: Title too short (16 chars, recommended min 30) The title tag is only 16 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
URL: Contains uppercase characters The URL contains uppercase characters. Lowercase URLs are preferred as they prevent duplicate content issues (some servers treat case differently) and are easier for users to type and remember.
CONTENT: Very low text-to-HTML ratio (5.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (431 KB, recommended <100KB) The page weighs 431 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog (3 findings)
▶
Finding Recommendation
META: Title too short (18 chars, recommended min 30) The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (104 KB, recommended <100KB) The page weighs 104 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2022/03/29/react-v18 (3 findings)
▶
Finding Recommendation
META: Title too short (19 chars, recommended min 30) The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (266 KB, recommended <100KB) The page weighs 266 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2023/03/16/introducing-react-dev (3 findings)
▶
Finding Recommendation
META: Title too short (29 chars, recommended min 30) The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (222 KB, recommended <100KB) The page weighs 222 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2024/12/05/react-19 (3 findings)
▶
Finding Recommendation
META: Title too short (17 chars, recommended min 30) The title tag is only 17 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (9.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (310 KB, recommended <100KB) The page weighs 310 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2025/10/01/react-19-2 (3 findings)
▶
Finding Recommendation
META: Title too short (18 chars, recommended min 30) The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (177 KB, recommended <100KB) The page weighs 177 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2025/10/07/react-compiler-1 (3 findings)
▶
Finding Recommendation
META: Title too short (27 chars, recommended min 30) The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (161 KB, recommended <100KB) The page weighs 161 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2026/09/09/react-19-3 (3 findings)
▶
Finding Recommendation
META: Title too short (18 chars, recommended min 30) The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (374 KB, recommended <100KB) The page weighs 374 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
community/team (3 findings)
▶
Finding Recommendation
META: Title too short (21 chars, recommended min 30) The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (397 KB, recommended <100KB) The page weighs 397 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn (3 findings)
▶
Finding Recommendation
META: Title too short (19 chars, recommended min 30) The title tag is only 19 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (258 KB, recommended <100KB) The page weighs 258 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/adding-interactivity (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (297 KB, recommended <100KB) The page weighs 297 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/conditional-rendering (3 findings)
▶
Finding Recommendation
META: Title too short (29 chars, recommended min 30) The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (283 KB, recommended <100KB) The page weighs 283 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/creating-a-react-app (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (142 KB, recommended <100KB) The page weighs 142 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/describing-the-ui (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (270 KB, recommended <100KB) The page weighs 270 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/editor-setup (3 findings)
▶
Finding Recommendation
META: Title too short (20 chars, recommended min 30) The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (113 KB, recommended <100KB) The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/escape-hatches (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (336 KB, recommended <100KB) The page weighs 336 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/installation (3 findings)
▶
Finding Recommendation
META: Title too short (20 chars, recommended min 30) The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (113 KB, recommended <100KB) The page weighs 113 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/managing-state (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (301 KB, recommended <100KB) The page weighs 301 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/react-compiler (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (103 KB, recommended <100KB) The page weighs 103 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/react-compiler/incremental-adoption (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (150 KB, recommended <100KB) The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/react-compiler/installation (3 findings)
▶
Finding Recommendation
META: Title too short (20 chars, recommended min 30) The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (182 KB, recommended <100KB) The page weighs 182 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/react-compiler/introduction (3 findings)
▶
Finding Recommendation
META: Title too short (20 chars, recommended min 30) The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (162 KB, recommended <100KB) The page weighs 162 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/react-developer-tools (3 findings)
▶
Finding Recommendation
META: Title too short (29 chars, recommended min 30) The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (107 KB, recommended <100KB) The page weighs 107 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/render-and-commit (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (167 KB, recommended <100KB) The page weighs 167 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/rendering-lists (3 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (4.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (265 KB, recommended <100KB) The page weighs 265 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/responding-to-events (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (321 KB, recommended <100KB) The page weighs 321 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/state-as-a-snapshot (3 findings)
▶
Finding Recommendation
META: Title too short (27 chars, recommended min 30) The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (227 KB, recommended <100KB) The page weighs 227 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/thinking-in-react (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (7.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (278 KB, recommended <100KB) The page weighs 278 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/tutorial-tic-tac-toe (3 findings)
▶
Finding Recommendation
META: Title too short (29 chars, recommended min 30) The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (8.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (940 KB, recommended <100KB) The page weighs 940 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/typescript (3 findings)
▶
Finding Recommendation
META: Title too short (24 chars, recommended min 30) The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (283 KB, recommended <100KB) The page weighs 283 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/your-first-component (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (5.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (198 KB, recommended <100KB) The page weighs 198 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react-compiler/compiling-libraries (3 findings)
▶
Finding Recommendation
META: Title too short (27 chars, recommended min 30) The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (170 KB, recommended <100KB) The page weighs 170 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react-compiler/configuration (3 findings)
▶
Finding Recommendation
META: Title too short (21 chars, recommended min 30) The title tag is only 21 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (164 KB, recommended <100KB) The page weighs 164 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react-compiler/directives (3 findings)
▶
Finding Recommendation
META: Title too short (18 chars, recommended min 30) The title tag is only 18 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (191 KB, recommended <100KB) The page weighs 191 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react-dom (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (158 KB, recommended <100KB) The page weighs 158 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react-dom/client (3 findings)
▶
Finding Recommendation
META: Title too short (29 chars, recommended min 30) The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (138 KB, recommended <100KB) The page weighs 138 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react-dom/components (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (323 KB, recommended <100KB) The page weighs 323 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react-dom/server (3 findings)
▶
Finding Recommendation
META: Title too short (29 chars, recommended min 30) The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (149 KB, recommended <100KB) The page weighs 149 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/apis (3 findings)
▶
Finding Recommendation
META: Title too short (27 chars, recommended min 30) The title tag is only 27 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (149 KB, recommended <100KB) The page weighs 149 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/hooks (3 findings)
▶
Finding Recommendation
META: Title too short (28 chars, recommended min 30) The title tag is only 28 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (173 KB, recommended <100KB) The page weighs 173 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/legacy (3 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (150 KB, recommended <100KB) The page weighs 150 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
versions (3 findings)
▶
Finding Recommendation
META: Title too short (22 chars, recommended min 30) The title tag is only 22 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (3.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (228 KB, recommended <100KB) The page weighs 228 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2021/06/08/the-plan-for-react-18 (2 findings)
▶
Finding Recommendation
META: Title too short (29 chars, recommended min 30) The title tag is only 29 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (6.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
blog/2022/03/08/react-18-upgrade-guide (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (9.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (177 KB, recommended <100KB) The page weighs 177 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2024/04/25/react-19-upgrade-guide (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (7.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (320 KB, recommended <100KB) The page weighs 320 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2024/10/21/react-compiler-beta-release (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (7.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (124 KB, recommended <100KB) The page weighs 124 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2025/12/03/critical-security-vulnerability-in-react-server-components (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (129 KB, recommended <100KB) The page weighs 129 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (6.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (130 KB, recommended <100KB) The page weighs 130 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
community (2 findings)
▶
Finding Recommendation
META: Title too short (23 chars, recommended min 30) The title tag is only 23 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
community/acknowledgements (2 findings)
▶
Finding Recommendation
META: Title too short (24 chars, recommended min 30) The title tag is only 24 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
community/docs-contributors (2 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.0%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
community/translations (2 findings)
▶
Finding Recommendation
META: Title too short (20 chars, recommended min 30) The title tag is only 20 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.8%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
community/versioning-policy (2 findings)
▶
Finding Recommendation
META: Title too short (25 chars, recommended min 30) The title tag is only 25 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
PERFORMANCE: Large page (131 KB, recommended <100KB) The page weighs 131 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/add-react-to-an-existing-project (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (156 KB, recommended <100KB) The page weighs 156 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/build-a-react-app-from-scratch (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (7.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (157 KB, recommended <100KB) The page weighs 157 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/choosing-the-state-structure (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (498 KB, recommended <100KB) The page weighs 498 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/extracting-state-logic-into-a-reducer (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (363 KB, recommended <100KB) The page weighs 363 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/importing-and-exporting-components (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (4.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (197 KB, recommended <100KB) The page weighs 197 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/javascript-in-jsx-with-curly-braces (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (3.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (218 KB, recommended <100KB) The page weighs 218 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/keeping-components-pure (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (231 KB, recommended <100KB) The page weighs 231 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/lifecycle-of-reactive-effects (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (7.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (430 KB, recommended <100KB) The page weighs 430 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/manipulating-the-dom-with-refs (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (353 KB, recommended <100KB) The page weighs 353 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/passing-data-deeply-with-context (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (345 KB, recommended <100KB) The page weighs 345 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/passing-props-to-a-component (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (4.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (260 KB, recommended <100KB) The page weighs 260 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/preserving-and-resetting-state (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (474 KB, recommended <100KB) The page weighs 474 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/queueing-a-series-of-state-updates (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (4.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (228 KB, recommended <100KB) The page weighs 228 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/react-compiler/debugging (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (4.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (117 KB, recommended <100KB) The page weighs 117 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/reacting-to-input-with-state (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.9%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (292 KB, recommended <100KB) The page weighs 292 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/referencing-values-with-refs (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (248 KB, recommended <100KB) The page weighs 248 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/removing-effect-dependencies (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (7.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (529 KB, recommended <100KB) The page weighs 529 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/reusing-logic-with-custom-hooks (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (6.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (595 KB, recommended <100KB) The page weighs 595 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/scaling-up-with-reducer-and-context (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.2%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (293 KB, recommended <100KB) The page weighs 293 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/separating-events-from-effects (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (6.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (412 KB, recommended <100KB) The page weighs 412 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/setup (2 findings)
▶
Finding Recommendation
META: Title too short (13 chars, recommended min 30) The title tag is only 13 characters. A more descriptive title (30-60 chars) would better communicate the page's topic to both users and search engines.
CONTENT: Very low text-to-HTML ratio (2.6%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
learn/sharing-state-between-components (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.5%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (233 KB, recommended <100KB) The page weighs 233 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/state-a-components-memory (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (6.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (338 KB, recommended <100KB) The page weighs 338 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/synchronizing-with-effects (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (8.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (499 KB, recommended <100KB) The page weighs 499 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/understanding-your-ui-as-a-tree (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (163 KB, recommended <100KB) The page weighs 163 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/updating-arrays-in-state (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.3%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (394 KB, recommended <100KB) The page weighs 394 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/updating-objects-in-state (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (5.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (5.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (355 KB, recommended <100KB) The page weighs 355 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/writing-markup-with-jsx (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (4.7%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (4.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (189 KB, recommended <100KB) The page weighs 189 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
learn/you-might-not-need-an-effect (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (9.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (424 KB, recommended <100KB) The page weighs 424 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (3.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (152 KB, recommended <100KB) The page weighs 152 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
reference/react/components (2 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (2.1%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (2.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
PERFORMANCE: Large page (140 KB, recommended <100KB) The page weighs 140 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times.
blog/2026/02/24/the-react-foundation (1 findings)
▶
Finding Recommendation
CONTENT: Very low text-to-HTML ratio (3.4%) This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (3.4%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance.
Implemented Well SEO Best Practices Implemented (2533 findings across 100 pages) ▲ Sections

These elements have been properly implemented, demonstrating strong SEO foundations. Click any page to expand its findings.

blog/2021/06/08/the-plan-for-react-18 (28 findings)
▶
meta Title tag present -- 29 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2021/06/08/the-plan-for-react-18
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- The Plan for React 18
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 948 words
The page has adequate content for search relevance.
content Strong content depth -- 948 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2021/06/08/the-plan-for-react-18/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 150ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 89 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog (27 findings)
▶
meta Title tag present -- 18 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Blog
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1347 words
The page has adequate content for search relevance.
content Strong content depth -- 1347 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 96ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2022/03/08/react-18-upgrade-guide (27 findings)
▶
meta Title tag present -- 34 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 34 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/blog/2022/03/08/react-18-upgrade-guide
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- How to Upgrade to React 18
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2837 words
The page has adequate content for search relevance.
content Strong content depth -- 2837 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2022/03/08/react-18-upgrade-guide/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 78ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2024/04/25/react-19-upgrade-guide (27 findings)
▶
meta Title tag present -- 30 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 30 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/blog/2024/04/25/react-19-upgrade-guide
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React 19 Upgrade Guide
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3863 words
The page has adequate content for search relevance.
content Strong content depth -- 3863 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2024/04/25/react-19-upgrade-guide/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 5 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 5 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 98ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2024/10/21/react-compiler-beta-release (27 findings)
▶
meta Title tag present -- 35 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 35 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/blog/2024/10/21/react-compiler-beta-release
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Compiler Beta Release
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1497 words
The page has adequate content for search relevance.
content Strong content depth -- 1497 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2024/10/21/react-compiler-beta-release/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 232ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2025/12/03/critical-security-vulnerability-in-react-server-components (27 findings)
▶
meta Title tag present -- 66 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Critical Security Vulnerability in React Server Components
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1164 words
The page has adequate content for search relevance.
content Strong content depth -- 1164 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2025/12/03/critical-security-vulnerability-in-react-server-components/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 60ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2026/09/09/react-19-3 (27 findings)
▶
meta Title tag present -- 18 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2026/09/09/react-19-3
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React 19.3
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 4365 words
The page has adequate content for search relevance.
content Strong content depth -- 4365 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2026/09/09/react-19-3/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 90ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
community/versioning-policy (27 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/community/versioning-policy
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Versioning Policy
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2331 words
The page has adequate content for search relevance.
content Strong content depth -- 2331 words
The page has substantial content, which tends to perform well in search.
content Healthy text-to-HTML ratio -- 10.8%
The page has a good balance of content vs. markup.
content Clean URL structure -- /community/versioning-policy/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 75ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react (27 findings)
▶
meta Title tag present -- 32 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 32 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/reference/react
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Reference Overview
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 637 words
The page has adequate content for search relevance.
content Strong content depth -- 637 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /reference/react/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 62ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2022/03/29/react-v18 (26 findings)
▶
meta Title tag present -- 19 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2022/03/29/react-v18
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React v18.0
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3968 words
The page has adequate content for search relevance.
content Strong content depth -- 3968 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2022/03/29/react-v18/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 132ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2024/12/05/react-19 (26 findings)
▶
meta Title tag present -- 17 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2024/12/05/react-19
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React v19
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 5063 words
The page has adequate content for search relevance.
content Strong content depth -- 5063 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2024/12/05/react-19/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 89ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2025/10/07/react-compiler-1 (26 findings)
▶
meta Title tag present -- 27 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2025/10/07/react-compiler-1
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Compiler v1.0
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1886 words
The page has adequate content for search relevance.
content Strong content depth -- 1886 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2025/10/07/react-compiler-1/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 114ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components (26 findings)
▶
meta Title tag present -- 77 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Denial of Service and Source Code Exposure in React Server Components
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1283 words
The page has adequate content for search relevance.
content Strong content depth -- 1283 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 51ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
community/acknowledgements (26 findings)
▶
meta Title tag present -- 24 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/community/acknowledgements
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Acknowledgements
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 344 words
The page has adequate content for search relevance.
content Clean URL structure -- /community/acknowledgements/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 253ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 98 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
community/translations (26 findings)
▶
meta Title tag present -- 20 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/community/translations
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Translations
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 457 words
The page has adequate content for search relevance.
content Clean URL structure -- /community/translations/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 65ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 98 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/add-react-to-an-existing-project (26 findings)
▶
meta Title tag present -- 40 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 40 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/add-react-to-an-existing-project
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Add React to an Existing Project
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1389 words
The page has adequate content for search relevance.
content Strong content depth -- 1389 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/add-react-to-an-existing-project/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 59ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/build-a-react-app-from-scratch (26 findings)
▶
meta Title tag present -- 38 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 38 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/build-a-react-app-from-scratch
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Build a React app from Scratch
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1930 words
The page has adequate content for search relevance.
content Strong content depth -- 1930 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/build-a-react-app-from-scratch/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 115ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/choosing-the-state-structure (26 findings)
▶
meta Title tag present -- 36 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 36 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/choosing-the-state-structure
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Choosing the State Structure
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 6065 words
The page has adequate content for search relevance.
content Strong content depth -- 6065 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/choosing-the-state-structure/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 208ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/extracting-state-logic-into-a-reducer (26 findings)
▶
meta Title tag present -- 45 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 45 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/extracting-state-logic-into-a-reducer
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Extracting State Logic into a Reducer
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3885 words
The page has adequate content for search relevance.
content Strong content depth -- 3885 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/extracting-state-logic-into-a-reducer/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 90ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/installation (26 findings)
▶
meta Title tag present -- 20 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/installation
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Installation
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 604 words
The page has adequate content for search relevance.
content Strong content depth -- 604 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/installation/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 73ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/javascript-in-jsx-with-curly-braces (26 findings)
▶
meta Title tag present -- 43 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 43 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/javascript-in-jsx-with-curly-braces
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- JavaScript in JSX with Curly Braces
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1567 words
The page has adequate content for search relevance.
content Strong content depth -- 1567 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/javascript-in-jsx-with-curly-braces/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 90ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/lifecycle-of-reactive-effects (26 findings)
▶
meta Title tag present -- 37 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 37 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/lifecycle-of-reactive-effects
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Lifecycle of Reactive Effects
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 6095 words
The page has adequate content for search relevance.
content Strong content depth -- 6095 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/lifecycle-of-reactive-effects/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 240ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/manipulating-the-dom-with-refs (26 findings)
▶
meta Title tag present -- 38 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 38 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/manipulating-the-dom-with-refs
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Manipulating the DOM with Refs
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 4011 words
The page has adequate content for search relevance.
content Strong content depth -- 4011 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/manipulating-the-dom-with-refs/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 202ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/passing-data-deeply-with-context (26 findings)
▶
meta Title tag present -- 40 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 40 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/passing-data-deeply-with-context
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Passing Data Deeply with Context
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3835 words
The page has adequate content for search relevance.
content Strong content depth -- 3835 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/passing-data-deeply-with-context/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 9 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 9 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 85ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/preserving-and-resetting-state (26 findings)
▶
meta Title tag present -- 38 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 38 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/preserving-and-resetting-state
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Preserving and Resetting State
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 5077 words
The page has adequate content for search relevance.
content Strong content depth -- 5077 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/preserving-and-resetting-state/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 25 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 25 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 100ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/react-compiler/debugging (26 findings)
▶
meta Title tag present -- 37 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 37 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/react-compiler/debugging
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Debugging and Troubleshooting
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 902 words
The page has adequate content for search relevance.
content Strong content depth -- 902 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/react-compiler/debugging/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 70ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/removing-effect-dependencies (26 findings)
▶
meta Title tag present -- 36 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 36 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/removing-effect-dependencies
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Removing Effect Dependencies
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 7718 words
The page has adequate content for search relevance.
content Strong content depth -- 7718 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/removing-effect-dependencies/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 85ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/reusing-logic-with-custom-hooks (26 findings)
▶
meta Title tag present -- 39 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 39 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/reusing-logic-with-custom-hooks
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Reusing Logic with Custom Hooks
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 7486 words
The page has adequate content for search relevance.
content Strong content depth -- 7486 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/reusing-logic-with-custom-hooks/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 95ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/scaling-up-with-reducer-and-context (26 findings)
▶
meta Title tag present -- 43 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 43 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/scaling-up-with-reducer-and-context
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Scaling Up with Reducer and Context
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3060 words
The page has adequate content for search relevance.
content Strong content depth -- 3060 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/scaling-up-with-reducer-and-context/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 107ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/separating-events-from-effects (26 findings)
▶
meta Title tag present -- 38 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 38 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/separating-events-from-effects
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Separating Events from Effects
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 5553 words
The page has adequate content for search relevance.
content Strong content depth -- 5553 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/separating-events-from-effects/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 84ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/setup (26 findings)
▶
meta Title tag present -- 13 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/setup
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Setup
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 405 words
The page has adequate content for search relevance.
content Clean URL structure -- /learn/setup/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 60ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 98 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/sharing-state-between-components (26 findings)
▶
meta Title tag present -- 40 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 40 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/sharing-state-between-components
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Sharing State Between Components
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2460 words
The page has adequate content for search relevance.
content Strong content depth -- 2460 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/sharing-state-between-components/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 9 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 9 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 85ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/state-a-components-memory (26 findings)
▶
meta Title tag present -- 35 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 35 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/state-a-components-memory
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- State: A Component's Memory
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3987 words
The page has adequate content for search relevance.
content Strong content depth -- 3987 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/state-a-components-memory/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 119ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/synchronizing-with-effects (26 findings)
▶
meta Title tag present -- 34 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 34 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/synchronizing-with-effects
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Synchronizing with Effects
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 7848 words
The page has adequate content for search relevance.
content Strong content depth -- 7848 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/synchronizing-with-effects/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 83ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/understanding-your-ui-as-a-tree (26 findings)
▶
meta Title tag present -- 39 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 39 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/understanding-your-ui-as-a-tree
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Understanding Your UI as a Tree
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1538 words
The page has adequate content for search relevance.
content Strong content depth -- 1538 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/understanding-your-ui-as-a-tree/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 9 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 9 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 72ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/updating-arrays-in-state (26 findings)
▶
meta Title tag present -- 32 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 32 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/updating-arrays-in-state
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Updating Arrays in State
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 4487 words
The page has adequate content for search relevance.
content Strong content depth -- 4487 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/updating-arrays-in-state/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 96ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/updating-objects-in-state (26 findings)
▶
meta Title tag present -- 33 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 33 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/updating-objects-in-state
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Updating Objects in State
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 4058 words
The page has adequate content for search relevance.
content Strong content depth -- 4058 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/updating-objects-in-state/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 156ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/writing-markup-with-jsx (26 findings)
▶
meta Title tag present -- 31 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 31 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/writing-markup-with-jsx
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Writing Markup with JSX
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1599 words
The page has adequate content for search relevance.
content Strong content depth -- 1599 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/writing-markup-with-jsx/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 9 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 9 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 80ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/you-might-not-need-an-effect (26 findings)
▶
meta Title tag present -- 36 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 36 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/you-might-not-need-an-effect
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- You Might Not Need an Effect
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 7437 words
The page has adequate content for search relevance.
content Strong content depth -- 7437 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/you-might-not-need-an-effect/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 92ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react-compiler/compiling-libraries (26 findings)
▶
meta Title tag present -- 27 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react-compiler/compiling-libraries
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Compiling Libraries
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 745 words
The page has adequate content for search relevance.
content Strong content depth -- 745 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /reference/react-compiler/compiling-libraries/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 61ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react-compiler/directives (26 findings)
▶
meta Title tag present -- 18 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react-compiler/directives
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Directives
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 970 words
The page has adequate content for search relevance.
content Strong content depth -- 970 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /reference/react-compiler/directives/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 62ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react-dom/components (26 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react-dom/components
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React DOM Components
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1097 words
The page has adequate content for search relevance.
content Strong content depth -- 1097 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /reference/react-dom/components/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 82ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/components (26 findings)
▶
meta Title tag present -- 33 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 33 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/reference/react/components
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Built-in React Components
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 359 words
The page has adequate content for search relevance.
content Clean URL structure -- /reference/react/components/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 181ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/hooks (26 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/hooks
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Built-in React Hooks
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1014 words
The page has adequate content for search relevance.
content Strong content depth -- 1014 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /reference/react/hooks/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 74ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
versions (26 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/versions
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Versions
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1078 words
The page has adequate content for search relevance.
content Strong content depth -- 1078 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /versions/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 72ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2023/03/16/introducing-react-dev (25 findings)
▶
meta Title tag present -- 29 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2023/03/16/introducing-react-dev
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Introducing react.dev
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2893 words
The page has adequate content for search relevance.
content Strong content depth -- 2893 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2023/03/16/introducing-react-dev/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 4 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 98ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2025/10/01/react-19-2 (25 findings)
▶
meta Title tag present -- 18 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2025/10/01/react-19-2
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React 19.2
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2088 words
The page has adequate content for search relevance.
content Strong content depth -- 2088 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /blog/2025/10/01/react-19-2/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 59ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
community (25 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/community
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Community
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Clean URL structure -- /community/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 64ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 76 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
community/docs-contributors (25 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/community/docs-contributors
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Docs Contributors
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Clean URL structure -- /community/docs-contributors/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 76ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 85 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
community/team (25 findings)
▶
meta Title tag present -- 21 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/community/team
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Meet the Team
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1846 words
The page has adequate content for search relevance.
content Strong content depth -- 1846 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /community/team/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 165 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 102ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn (25 findings)
▶
meta Title tag present -- 19 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Quick Start
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2771 words
The page has adequate content for search relevance.
content Strong content depth -- 2771 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 9 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 9 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 84ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/conditional-rendering (25 findings)
▶
meta Title tag present -- 29 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/conditional-rendering
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Conditional Rendering
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2697 words
The page has adequate content for search relevance.
content Strong content depth -- 2697 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/conditional-rendering/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 95ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/creating-a-react-app (25 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/creating-a-react-app
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Creating a React App
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1226 words
The page has adequate content for search relevance.
content Strong content depth -- 1226 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/creating-a-react-app/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 73ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/describing-the-ui (25 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/describing-the-ui
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Describing the UI
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2212 words
The page has adequate content for search relevance.
content Strong content depth -- 2212 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/describing-the-ui/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 5 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 5 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 63ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/editor-setup (25 findings)
▶
meta Title tag present -- 20 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/editor-setup
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Editor Setup
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 774 words
The page has adequate content for search relevance.
content Strong content depth -- 774 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/editor-setup/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 64ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/escape-hatches (25 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/escape-hatches
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Escape Hatches
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3801 words
The page has adequate content for search relevance.
content Strong content depth -- 3801 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/escape-hatches/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 82ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/importing-and-exporting-components (25 findings)
▶
meta Title tag present -- 42 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 42 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/importing-and-exporting-components
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Importing and Exporting Components
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1574 words
The page has adequate content for search relevance.
content Strong content depth -- 1574 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/importing-and-exporting-components/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 2 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 60ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/keeping-components-pure (25 findings)
▶
meta Title tag present -- 31 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 31 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/keeping-components-pure
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Keeping Components Pure
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2344 words
The page has adequate content for search relevance.
content Strong content depth -- 2344 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/keeping-components-pure/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 2 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 76ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/managing-state (25 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/managing-state
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Managing State
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3120 words
The page has adequate content for search relevance.
content Strong content depth -- 3120 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/managing-state/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 116ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/passing-props-to-a-component (25 findings)
▶
meta Title tag present -- 36 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 36 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/passing-props-to-a-component
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Passing Props to a Component
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2329 words
The page has adequate content for search relevance.
content Strong content depth -- 2329 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/passing-props-to-a-component/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 2 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 82ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/queueing-a-series-of-state-updates (25 findings)
▶
meta Title tag present -- 42 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 42 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/queueing-a-series-of-state-updates
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Queueing a Series of State Updates
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2251 words
The page has adequate content for search relevance.
content Strong content depth -- 2251 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/queueing-a-series-of-state-updates/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 2 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 75ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/react-compiler (25 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/react-compiler
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Compiler
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 431 words
The page has adequate content for search relevance.
content Clean URL structure -- /learn/react-compiler/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 75ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/react-compiler/incremental-adoption (25 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/react-compiler/incremental-adoption
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Incremental Adoption
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1266 words
The page has adequate content for search relevance.
content Strong content depth -- 1266 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/react-compiler/incremental-adoption/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 174ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/react-compiler/installation (25 findings)
▶
meta Title tag present -- 20 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/react-compiler/installation
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Installation
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1326 words
The page has adequate content for search relevance.
content Strong content depth -- 1326 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/react-compiler/installation/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 58ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/react-compiler/introduction (25 findings)
▶
meta Title tag present -- 20 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/react-compiler/introduction
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Introduction
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1723 words
The page has adequate content for search relevance.
content Strong content depth -- 1723 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/react-compiler/introduction/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/reacting-to-input-with-state (25 findings)
▶
meta Title tag present -- 36 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 36 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/reacting-to-input-with-state
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Reacting to Input with State
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3219 words
The page has adequate content for search relevance.
content Strong content depth -- 3219 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/reacting-to-input-with-state/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 7 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 77ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/referencing-values-with-refs (25 findings)
▶
meta Title tag present -- 36 chars
The page has a title tag, which is essential for search results.
meta Title length is ideal -- 36 chars
The title is within the recommended 30-60 character range for search results.
meta Canonical URL set -- https://react.dev/learn/referencing-values-with-refs
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Referencing Values with Refs
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2588 words
The page has adequate content for search relevance.
content Strong content depth -- 2588 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/referencing-values-with-refs/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 2 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 101ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/rendering-lists (25 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/rendering-lists
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Rendering Lists
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2466 words
The page has adequate content for search relevance.
content Strong content depth -- 2466 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/rendering-lists/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 230ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/responding-to-events (25 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/responding-to-events
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Responding to Events
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3174 words
The page has adequate content for search relevance.
content Strong content depth -- 3174 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/responding-to-events/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 77ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/typescript (25 findings)
▶
meta Title tag present -- 24 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/typescript
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Using TypeScript
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3111 words
The page has adequate content for search relevance.
content Strong content depth -- 3111 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/typescript/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 70ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/your-first-component (25 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/your-first-component
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Your First Component
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1738 words
The page has adequate content for search relevance.
content Strong content depth -- 1738 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/your-first-component/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 83ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react-compiler/configuration (25 findings)
▶
meta Title tag present -- 21 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react-compiler/configuration
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Configuration
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 628 words
The page has adequate content for search relevance.
content Strong content depth -- 628 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /reference/react-compiler/configuration/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 166ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react-dom (25 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react-dom
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React DOM APIs
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 588 words
The page has adequate content for search relevance.
content Clean URL structure -- /reference/react-dom/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 56ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react-dom/client (25 findings)
▶
meta Title tag present -- 29 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react-dom/client
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Client React DOM APIs
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 370 words
The page has adequate content for search relevance.
content Clean URL structure -- /reference/react-dom/client/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 166ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react-dom/server (25 findings)
▶
meta Title tag present -- 29 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react-dom/server
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Server React DOM APIs
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 464 words
The page has adequate content for search relevance.
content Clean URL structure -- /reference/react-dom/server/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 194ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/apis (25 findings)
▶
meta Title tag present -- 27 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/apis
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Built-in React APIs
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 518 words
The page has adequate content for search relevance.
content Clean URL structure -- /reference/react/apis/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 58ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/legacy (25 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/legacy
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Legacy React APIs
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 455 words
The page has adequate content for search relevance.
content Clean URL structure -- /reference/react/legacy/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 189ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/usecontext (25 findings)
▶
meta Title tag present -- 18 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useContext
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useContext
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 2908 words
The page has adequate content for search relevance.
content Strong content depth -- 2908 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 140ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/useimperativehandle (25 findings)
▶
meta Title tag present -- 27 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useImperativeHandle
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useImperativeHandle
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 1226 words
The page has adequate content for search relevance.
content Strong content depth -- 1226 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 228ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/usereducer (25 findings)
▶
meta Title tag present -- 18 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useReducer
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useReducer
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 3730 words
The page has adequate content for search relevance.
content Strong content depth -- 3730 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 75ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
/ (24 findings)
▶
meta Title tag present -- 5 chars
The page has a title tag, which is essential for search results.
meta Meta description present -- 260 chars
The page has a meta description for search result snippets.
meta Canonical URL set -- https://react.dev/
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Sufficient content depth -- 1436 words
The page has adequate content for search relevance.
content Strong content depth -- 1436 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 90ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
blog/2026/02/24/the-react-foundation (24 findings)
▶
meta Title tag present -- 81 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/blog/2026/02/24/the-react-foundation
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- The React Foundation: A New Home for React Hosted by the Linux Foundation
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 422 words
The page has adequate content for search relevance.
content Clean URL structure -- /blog/2026/02/24/the-react-foundation/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 53ms
The server responded in under 500ms -- excellent performance.
performance Compact page size -- 76 KB
The page HTML is under 100KB, contributing to fast load times.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links All links are crawlable -- Crawlable
No JavaScript-only links -- search engines can follow all links.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/adding-interactivity (24 findings)
▶
meta Title tag present -- 28 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/adding-interactivity
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Adding Interactivity
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2886 words
The page has adequate content for search relevance.
content Strong content depth -- 2886 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/adding-interactivity/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 4 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 130ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/render-and-commit (24 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/render-and-commit
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Render and Commit
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1314 words
The page has adequate content for search relevance.
content Strong content depth -- 1314 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/render-and-commit/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 8 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 59ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/thinking-in-react (24 findings)
▶
meta Title tag present -- 25 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/thinking-in-react
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Thinking in React
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 4277 words
The page has adequate content for search relevance.
content Strong content depth -- 4277 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/thinking-in-react/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have dimensions -- 3 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 68ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/tutorial-tic-tac-toe (24 findings)
▶
meta Title tag present -- 29 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/tutorial-tic-tac-toe
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- Tutorial: Tic-Tac-Toe
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 16585 words
The page has adequate content for search relevance.
content Strong content depth -- 16585 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/tutorial-tic-tac-toe/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 17 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 103ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/useactionstate (24 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useActionState
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useActionState
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 5150 words
The page has adequate content for search relevance.
content Strong content depth -- 5150 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 82ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/usecallback (24 findings)
▶
meta Title tag present -- 19 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useCallback
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useCallback
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 4294 words
The page has adequate content for search relevance.
content Strong content depth -- 4294 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 127ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/usedebugvalue (24 findings)
▶
meta Title tag present -- 21 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useDebugValue
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useDebugValue
The page has exactly one H1 heading, clearly defining its main topic.
content Proper heading hierarchy -- Valid hierarchy
Headings follow a logical order (no skipped levels), aiding content structure.
content Sufficient content depth -- 749 words
The page has adequate content for search relevance.
content Strong content depth -- 749 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 2 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 195ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/usedeferredvalue (24 findings)
▶
meta Title tag present -- 24 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useDeferredValue
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useDeferredValue
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2762 words
The page has adequate content for search relevance.
content Strong content depth -- 2762 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 78ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/useeffect (24 findings)
▶
meta Title tag present -- 17 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useEffect
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useEffect
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 7755 words
The page has adequate content for search relevance.
content Strong content depth -- 7755 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 86ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/useeffectevent (24 findings)
▶
meta Title tag present -- 22 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useEffectEvent
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useEffectEvent
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 3095 words
The page has adequate content for search relevance.
content Strong content depth -- 3095 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 84ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/useid (24 findings)
▶
meta Title tag present -- 13 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useId
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useId
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1552 words
The page has adequate content for search relevance.
content Strong content depth -- 1552 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 58ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/useinsertioneffect (24 findings)
▶
meta Title tag present -- 26 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useInsertionEffect
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useInsertionEffect
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 1142 words
The page has adequate content for search relevance.
content Strong content depth -- 1142 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 178ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/uselayouteffect (24 findings)
▶
meta Title tag present -- 23 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useLayoutEffect
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useLayoutEffect
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2119 words
The page has adequate content for search relevance.
content Strong content depth -- 2119 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 83ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/usememo (24 findings)
▶
meta Title tag present -- 15 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useMemo
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useMemo
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 5836 words
The page has adequate content for search relevance.
content Strong content depth -- 5836 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 97ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/useoptimistic (24 findings)
▶
meta Title tag present -- 21 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useOptimistic
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useOptimistic
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 5038 words
The page has adequate content for search relevance.
content Strong content depth -- 5038 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 86ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
reference/react/usestate (24 findings)
▶
meta Title tag present -- 16 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/reference/react/useState
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- useState
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 4795 words
The page has adequate content for search relevance.
content Strong content depth -- 4795 words
The page has substantial content, which tends to perform well in search.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 1 images
Every image on the page includes an alt attribute for accessibility.
accessibility All images have dimensions -- 1 images
Images include explicit dimensions or aspect-ratio hints, preventing layout shifts.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 83ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/react-developer-tools (23 findings)
▶
meta Title tag present -- 29 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/react-developer-tools
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- React Developer Tools
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 514 words
The page has adequate content for search relevance.
content Clean URL structure -- /learn/react-developer-tools/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility All images have alt text -- 3 images
Every image on the page includes an alt attribute for accessibility.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 83ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
learn/state-as-a-snapshot (23 findings)
▶
meta Title tag present -- 27 chars
The page has a title tag, which is essential for search results.
meta Canonical URL set -- https://react.dev/learn/state-as-a-snapshot
A canonical URL is defined, helping prevent duplicate content issues.
meta Self-referencing canonical -- Self-referencing
The canonical URL correctly points to this page itself.
meta Character encoding declared -- utf-8
The character encoding is properly declared for consistent text rendering.
meta Page is indexable -- Indexable
No noindex directives found -- search engines can index this page.
meta HTML lang attribute set -- en
The page language is declared, aiding search engines and accessibility tools.
meta Meta viewport configured -- Present
The viewport is configured for mobile-responsive rendering.
technical HTTPS enforced -- Secure
The page is served over HTTPS, providing encryption and trust signals.
technical HSTS header present -- Enabled
Strict-Transport-Security header is set, enforcing HTTPS connections.
technical HTTP 200 OK status -- 200
The page returns a successful HTTP 200 response.
content Single H1 heading -- State as a Snapshot
The page has exactly one H1 heading, clearly defining its main topic.
content Sufficient content depth -- 2359 words
The page has adequate content for search relevance.
content Strong content depth -- 2359 words
The page has substantial content, which tends to perform well in search.
content Clean URL structure -- /learn/state-as-a-snapshot/
The URL is lowercase and concise, following best practices.
social Open Graph tags complete -- 4/4
All four OG tags (title, description, image, url) are present for social sharing.
social OG URL matches canonical -- Aligned
The og:url aligns with the canonical URL, ensuring consistent signals.
social Twitter Card configured -- summary_large_image
Twitter Card meta tags are set for optimized Twitter/X sharing.
accessibility No deprecated HTML elements -- Clean markup
The page uses modern HTML standards without deprecated elements.
performance Fast response time -- 64ms
The server responded in under 500ms -- excellent performance.
performance Compression enabled -- gzip
The server uses gzip compression to reduce transfer size.
performance No render-blocking scripts -- All deferred
All external scripts use async or defer, allowing fast page rendering.
links No mixed-content links -- All HTTPS
All links use HTTPS, maintaining a consistent secure experience.
links Secure external links -- Secure
External links opening in new tabs include rel='noopener' for security.
301 Redirect Plan

Recommended 301 permanent redirects from legacy.reactjs.org (old docs, kept online) to react.dev (new docs). These redirects help preserve search engine rankings and ensure visitors find the right pages after the migration.

Old Path New Path Source Confidence Notes Live Today Matches Plan
/ / Exact 100% Redirected Yes
/blog/2022/03/08/react-18-upgrade-guide.html /blog/2022/03/08/react-18-upgrade-guide title 100% Title similarity: 100% Redirected Yes
/docs/conditional-rendering.html /learn/conditional-rendering title 100% Title similarity: 100% Redirected No -- live: https://legacy.reactjs.org/docs/conditional-rendering.html; plan: https://react.dev/learn/conditional-rendering/
/docs/faq-versioning.html /community/versioning-policy title 100% Title similarity: 100% Redirected No -- live: https://legacy.reactjs.org/docs/faq-versioning.html; plan: https://react.dev/community/versioning-policy/
/versions /versions Exact 100% Redirected No -- live: https://legacy.reactjs.org/versions; plan: https://react.dev/versions/
/blog/2017/04/07/react-v15.5.0.html /blog/2022/03/29/react-v18 title 83% Title similarity: 83% Redirected No -- live: https://legacy.reactjs.org/blog/2017/04/07/react-v15.5.0.html; plan: https://react.dev/blog/2022/03/29/react-v18/
/docs/context.html /reference/react/usecontext title 82% Title similarity: 82% Redirected No -- live: https://legacy.reactjs.org/docs/context.html; plan: https://react.dev/reference/react/useContext/
/acknowledgements.html /community/acknowledgements title 80% Title similarity: 80% Redirected No -- live: https://legacy.reactjs.org/acknowledgements.html; plan: https://react.dev/community/acknowledgements/
/docs/react-component.html /reference/react-dom/components title 80% Title similarity: 80% Redirected No -- live: https://legacy.reactjs.org/docs/react-component.html; plan: https://react.dev/reference/react-dom/components/
/docs/rendering-elements.html /learn/rendering-lists title 78% Title similarity: 79% Redirected No -- live: https://legacy.reactjs.org/docs/rendering-elements.html; plan: https://react.dev/learn/rendering-lists/
/docs/faq-functions.html /learn/passing-props-to-a-component title 77% Title similarity: 78% Redirected No -- live: https://legacy.reactjs.org/docs/faq-functions.html; plan: https://react.dev/learn/passing-props-to-a-component/
/docs/refs-and-the-dom.html /learn/manipulating-the-dom-with-refs Keyword 66% Keyword overlap: 67% Redirected No -- live: https://legacy.reactjs.org/docs/refs-and-the-dom.html; plan: https://react.dev/learn/manipulating-the-dom-with-refs/
/blog/2017/09/08/dom-attributes-in-react-16.html /reference/react-dom Keyword 50% Keyword overlap: 50% Redirected No -- live: https://legacy.reactjs.org/blog/2017/09/08/dom-attributes-in-react-16.html; plan: https://react.dev/reference/react-dom/
/blog/2015/12/18/react-components-elements-and-instances.html /reference/react/components Keyword 40% Keyword overlap: 40% Redirected No -- live: https://legacy.reactjs.org/blog/2015/12/18/react-components-elements-and-instances.html; plan: https://react.dev/reference/react/components/
/blog (needs redirect target) origin_error 0% Old page failed when crawled (HTTP 404); not compared and not counted as missing -- --
/blog/2016/02/19/new-versioning-scheme.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/blog/2016/07/13/mixins-considered-harmful.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/blog/2017/07/26/error-handling-in-react-16.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/blog/2017/11/28/react-v16.2.0-fragment-support.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/blog/2018/03/27/update-on-async-rendering.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/blog/2018/06/07/you-probably-dont-need-derived-state.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/blog/2018/09/10/introducing-the-react-profiler.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/blog/2018/11/27/react-16-roadmap.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/community/support.html (needs redirect target) unmatched 0% No equivalent page found on the new site To parent section --
/docs/accessibility.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/add-react-to-a-website.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/cdn-links.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/code-splitting.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/codebase-overview.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/components-and-props.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/composition-vs-inheritance.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/create-a-new-react-app.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/design-principles.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/dom-elements.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/error-boundaries.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/events.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/faq-ajax.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/faq-build.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/faq-internals.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/faq-state.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/faq-structure.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/faq-styling.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/forms.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/forwarding-refs.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/fragments.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/getting-started.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/glossary.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/handling-events.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/hello-world.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/higher-order-components.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/hooks-custom.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/hooks-effect.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/hooks-faq.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/hooks-intro.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/hooks-overview.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/hooks-reference.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/hooks-rules.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/hooks-state.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/how-to-contribute.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/implementation-notes.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/integrating-with-other-libraries.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/introducing-jsx.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/javascript-environment-requirements.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/jsx-in-depth.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/legacy-context.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/legacy-event-pooling.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/lifting-state-up.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/lists-and-keys.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/more-about-refs.html (needs redirect target) origin_error 0% Old page failed when crawled (HTTP 404); not compared and not counted as missing -- --
/docs/optimizing-performance.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/portals.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/profiler.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/react-api.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/react-dom-client.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/react-dom-server.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/react-dom.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/react-without-es6.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/react-without-jsx.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/reconciliation.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/release-channels.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/render-props.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/state-and-lifecycle.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/static-type-checking.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/strict-mode.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/test-renderer.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/test-utils.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/testing-environments.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/testing-recipes.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/testing.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/thinking-in-react.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/typechecking-with-proptypes.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/uncontrolled-components.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/web-components.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/docs/webcomponents.html (needs redirect target) origin_error 0% Old page failed when crawled (HTTP 404); not compared and not counted as missing -- --
/languages (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/redirect-to-codepen/reconciliation/index-used-as-key (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/redirect-to-codepen/reconciliation/no-index-used-as-key (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/redirect-to-codepen/uncontrolled-components/input-type-file (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/tutorial/tutorial.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --
/warnings/unknown-prop.html (needs redirect target) unmatched 0% No equivalent page found on the new site Redirected --