26 of 100 pages from the November 2013 archive have a counterpart today; 74 do not.
Health: At Risk, based on 100 archived pages and 101 pages crawled from python.org (live today) today; 75 pages exist only on today's site.
Nothing was set aside before analysis.
Note: The crawl of today's site stopped at 100 pages, so "no counterpart" means none was found among the pages crawled.
Note: The archive reconstruction stopped at 100 pages; old pages beyond that were not compared.
Note: Archived pages were captured between May 2012 and November 2013.
Working well: 26 matched pages improved, pages on today's site average 1,074 words, and the average response time is 110 ms. 21 of 21 matched pages gained structured data. 21 of 21 matched pages gained social preview tags.
Cross-page analysis of SEO fundamentals across the destination site.
| Metric | python.org (Wayback Machine, December 2013) | python.org (live today) | Change |
|---|---|---|---|
| Total Pages | 100 | 101 | +1 |
| Total Issues | 1229 | 828 | -401 |
| Priority Issues | 30 | 8 | -22 |
| Site Health | Needs Attention | Needs Attention |
| Sub-Score | Points | What 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 |
| Sub-Score | Points | What 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 |
| Sub-Score | Points | What Was Measured |
|---|---|---|
| Service pages | 1/None | 1 pages |
| Content-rich (300+ words) | 1/1 | 1 of 1 |
| With review schema | 0/1 | 0 of 1 |
| Sub-Score | Points | What 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 |
| Sub-Score | Points | What Was Measured |
|---|---|---|
| Avg word count | 4/4 | 1445 words (content pages) |
| Meta description coverage | 4/4 | 96% (96/100) |
| Title uniqueness | 1/4 | 57.0% unique |
| H1 quality | 3/4 | 74% of pages have exactly 1 H1 |
| Content uniqueness | 2/4 | 2 near-duplicate group(s) |
| Sub-Score | Points | What Was Measured |
|---|---|---|
| Avg word count | 4/4 | 1083 words (content pages) |
| Meta description coverage | 4/4 | 98% (99/101) |
| Title uniqueness | 3/4 | 84.8% unique |
| H1 quality | 2/4 | 50% of pages have exactly 1 H1 |
| Content uniqueness | 4/4 | 0 near-duplicate group(s) |
| Sub-Score | Points | What 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 | 2/4 | Archived: performance/security metrics unavailable from Wayback Machine, neutral score applied (2/4) |
| Sub-Score | Points | What Was Measured |
|---|---|---|
| Sitemap coverage | 0/4 | 0% (0/101) |
| Schema coverage | 3/4 | 98.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: 98%, avg response: 110ms, HSTS: yes |
| Sub-Score | Points | What 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 22.9 links/page |
| Differentiated content | 0/4 | 0 schema types, FAQ: no |
| Sub-Score | Points | What Was Measured |
|---|---|---|
| Brand consistency | 3/4 | 66% of titles |
| Review signals | 0/4 | 0 pages, 0 reviews |
| Local business signals | 0/4 | 0 pages, 0 complete |
| Internal linking | 4/4 | avg 114.5 links/page |
| Differentiated content | 0/4 | 1 schema types, FAQ: no |
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.
| Severity | Count | Description |
|---|---|---|
| Implemented Well | 2291 | SEO best practices properly implemented. Great work! |
| Pre-Launch Priority | 8 | Issues that directly impact SEO rankings or user experience and should be addressed before launch. |
| Recommended | 494 | Improvements that would strengthen the site's search presence and overall quality. |
| Informational | 326 | Minor observations and nice-to-have improvements for reference. |
5 checks: 2 pass, 2 warn, 1 info. Checks on python.org (live today); analytics and verification tags compared with python.org (Wayback Machine, December 2013). Based on what Webtrace can see from outside the site (21 extra requests).
| Status | Check | Finding |
|---|---|---|
| Pass | One canonical address |
Every host form reaches https://www.python.org in one permanent redirect, and deep links keep their path.
https://www.python.org/ (200); HSTS on
|
| Pass | Unknown URLs return 404 |
An address that does not exist answers 404 (Not Found).
https://www.python.org/webtrace-soft-404-check-535d440cac97/ (404)
|
| Warn | Discovery files (robots.txt and sitemap) |
No XML sitemap was found at the standard addresses, and robots.txt declares none.
https://www.python.org/robots.txt (200, 537 bytes, 0 Sitemap lines)
What to do: Publish an XML sitemap and declare it in robots.txt with a Sitemap: line.
|
| Warn | Analytics tags |
No analytics tag found in page HTML on either site.
|
| Info | Ownership verification tags |
Neither homepage carries verification meta tags.
|
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.
Archived pages come from the Wayback Machine; tags the archive did not capture cannot be compared.
The archived homepage across its whole life in the Wayback Machine: every redesign, platform switch, analytics change and domain move, dated by the first capture that shows it.
| First seen | Lane | Change | Before | After | Date | Evidence |
|---|---|---|---|---|---|---|
| Jan 2026
last before: Dec 2025 |
Analytics | Analytics: UA-39055973-1 no longer found in HTML | UA-39055973-1 | None found in HTML | to the month |
Universal Analytics stopped processing data on July 1, 2023.
|
| May 2025
last before: Apr 2025 |
Analytics | Analytics: G-TF35YF9CVH, python.org no longer found in HTML | G-TF35YF9CVH, python.org, UA-39055973-1 | UA-39055973-1 | approximateseen once |
|
| Jun 2024
last before: May 2024 |
Analytics | Analytics: python.org added | G-TF35YF9CVH, UA-39055973-1 | G-TF35YF9CVH, python.org, UA-39055973-1 | approximateseen once |
|
| Mar 2023
last before: Jan 2023 |
Analytics | Analytics: G-TF35YF9CVH added | UA-39055973-1 | G-TF35YF9CVH, UA-39055973-1 | within 2 months |
|
| Mar 2014
last before: Feb 2014 |
Analytics | Analytics: UA-39055973-1 added | None found in HTML | UA-39055973-1 | to the month |
|
| Mar 2014
last before: Feb 2014 |
Design | Redesign | -- | -- | to the month |
|
| May 2006
last before: Feb 2006 |
Design | Redesign | -- | -- | within 6 months |
|
| Nov 2004
last before: Oct 2004 |
Design | Redesign | -- | -- | to the month |
|
| First seen | Field | Before | After |
|---|---|---|---|
| Oct 2026 seen once | H1 | Intuitive Interpretation | |
| Jan 2024 | Footer credit | (none) | |
| May 2019 | Footer credit | Powered by Heroku | |
| Dec 2017 | Footer credit | Powered by Rackspace | |
| Apr 2015 | Schema types | WebSite | |
| Aug 2014 | H1 | Functions Defined | |
| Mar 2014 | Title | Welcome to Python.org | |
| Mar 2014 | Meta description | The official home of the Python Programming Language | |
| Mar 2014 | H1 | Intuitive Interpretation | |
| Dec 2013 | Meta description | Home page for Python, an interactive, object-oriented, extensible programming language. It provides an extraordinary combination of clarity and versatility, and is free, open-source, and comprehens... | |
| Mar 2011 | Title | Python Programming Language – Official Website | |
| Mar 2011 | H1 | Python Programming Language – Official Website | |
| Aug 2007 | H1 | Python Programming Language -- Official Website | |
| May 2006 | Title | Python Programming Language -- Official Website | |
| May 2006 | HTML lang | en | |
| May 2006 | H1 | The Python Programming Language | |
| May 2006 | Generator | (none) | |
| Dec 2003 | Title | Python Programming Language | |
| May 2002 | Generator | HT2HTML/2.0 | |
| Jan 1999 | Title | Python Language Website |
Set one of these as wayback.target_timestamp in project.json to compare that design with today's site.
| Design | wayback.target_timestamp | |
|---|---|---|
| Design 1 (May 1997 to Oct 2004) | 20041001073656 |
view capture |
| Design 2 (Nov 2004 to Feb 2006) | 20060202003017 |
view capture |
| Design 3 (May 2006 to Feb 2014) | 20140202234850 |
suggested baseline view capture |
| Design 4 (Mar 2014 to Oct 2026) | 20261001005540 |
view capture |
| URL | Title | Status | Words | Issues | Health |
|---|---|---|---|---|---|
| sponsors/application | Sponsorship Application | Python.org | 200 | 3440 | 13 | Needs Attention |
|
|||||
| downloads | Download Python | Python.org | 200 | 3319 | 12 | Needs Attention |
|
|||||
| psf/news-and-community | Python Software Foundation News & Community |... | 200 | 507 | 11 | Needs Attention |
|
|||||
| community/diversity | Diversity | Python.org | 200 | 565 | 10 | Needs Attention |
|
|||||
| download/other | Download Python for other platforms | Python.org | 200 | 858 | 10 | Needs Attention |
|
|||||
| events | Our Events | Python.org | 200 | 764 | 10 | At Risk |
|
|||||
| events/python-events | Our Events | Python.org | 200 | 447 | 10 | At Risk |
|
|||||
| events/python-events/2188 | PyConFR 2026 | Python.org | 200 | 368 | 10 | Needs Attention |
|
|||||
| events/python-events/past | Our Events | Python.org | 200 | 454 | 10 | At Risk |
|
|||||
| events/python-user-group | Our Events | Python.org | 200 | 478 | 10 | At Risk |
|
|||||
| events/python-user-group/past | Our Events | Python.org | 200 | 466 | 10 | At Risk |
|
|||||
| psf/donations | Support the PSF with a Donation or by becoming... | 200 | 807 | 10 | Needs Attention |
|
|||||
| psf/prospectus2026 | PyCon US and PSF Prospectus 2025-26 | Python.org | 200 | 355 | 10 | Needs Attention |
|
|||||
| psf/records/staff | Python Software Foundation Staff | Python... | 200 | 1668 | 10 | Needs Attention |
|
|||||
| psf/volunteer/pycon | Volunteer Opportunities for PyCon US | Python... | 200 | 499 | 10 | Needs Attention |
|
|||||
| about/apps | Applications for Python | Python.org | 200 | 743 | 9 | Needs Attention |
|
|||||
| about/gettingstarted | Python For Beginners | Python.org | 200 | 805 | 9 | Needs Attention |
|
|||||
| about/help | Help | Python.org | 200 | 729 | 9 | Needs Attention |
|
|||||
| about/quotes | Quotes about Python | Python.org | 200 | 1293 | 9 | Needs Attention |
|
|||||
| community | Our Community | Python.org | 200 | 605 | 9 | Needs Attention |
|
|||||
| community/forums | Forums | Python.org | 200 | 381 | 9 | Needs Attention |
|
|||||
| community/irc | Internet Relay Chat | Python.org | 200 | 547 | 9 | Needs Attention |
|
|||||
| community/lists | Mailing lists | Python.org | 200 | 1419 | 9 | Needs Attention |
|
|||||
| community/sigs | Python Special Interest Groups | Python.org | 200 | 765 | 9 | Needs Attention |
|
|||||
| dev/security | Python Security | Python.org | 200 | 817 | 9 | Needs Attention |
|
|||||
| doc/essays | Python Documentation Index | Python.org | 200 | 940 | 9 | Needs Attention |
|
|||||
| events/python-events/2150 | PyCon ES 2026 | Python.org | 200 | 373 | 9 | Needs Attention |
|
|||||
| events/python-events/2180 | PyBeach 2026 | Python.org | 200 | 368 | 9 | Needs Attention |
|
|||||
| events/python-user-group/2249 | Edmonton.py: The Edmonton Python User Group |... | 200 | 402 | 9 | Needs Attention |
|
|||||
| jobs/types | Our Job Types | Python.org | 200 | 444 | 9 | Needs Attention |
|
|||||
| psf-landing | Python Software Foundation | 200 | 645 | 9 | Needs Attention |
|
|||||
| psf/about | About the Python Software Foundation | Python... | 200 | 731 | 9 | Needs Attention |
|
|||||
| psf/about/legal-and-policies | Legal & Policies | Python Software Foundation | 200 | 428 | 9 | Needs Attention |
|
|||||
| psf/faq | Python Software Foundation FAQ | Python... | 200 | 789 | 9 | Needs Attention |
|
|||||
| psf/fiscal-sponsorees | Fiscal Sponsorees | Python Software Foundation | 200 | 1876 | 9 | Needs Attention |
|
|||||
| psf/newsletter | PSF Newsletter Signup | Python Software Foundation | 200 | 502 | 9 | Needs Attention |
|
|||||
| psf/sponsors | Python Software Foundation Sponsors | Python... | 200 | 542 | 9 | Needs Attention |
|
|||||
| psf/volunteer | Volunteer | Python Software Foundation | 200 | 502 | 9 | Needs Attention |
|
|||||
| psf/workgroups | Work Groups of the Python Software Foundation... | 200 | 2169 | 9 | Needs Attention |
|
|||||
| shell | Welcome to Python.org | 200 | 716 | 9 | At Risk |
|
|||||
| / | Welcome to Python.org | 200 | 1101 | 8 | Needs Attention |
|
|||||
| about | About Pythonâ„¢ | Python.org | 200 | 666 | 8 | Needs Attention |
|
|||||
| about/legal | Legal Statements | Python Software Foundation | 200 | 716 | 8 | Needs Attention |
|
|||||
| blogs | Our Blogs | Python.org | 200 | 575 | 8 | Needs Attention |
|
|||||
| community/awards | Python Community Awards | Python Software Foundation | 200 | 429 | 8 | Needs Attention |
|
|||||
| community/logos | The Python Logo | Python Software Foundation | 200 | 695 | 8 | Needs Attention |
|
|||||
| community/workshops | Conferences and Workshops | Python.org | 200 | 522 | 8 | Needs Attention |
|
|||||
| dev | Python Developer's Guide | Python.org | 200 | 361 | 8 | Needs Attention |
|
|||||
| dev/core-mentorship | Python Core Mentorship | Python.org | 200 | 802 | 8 | Needs Attention |
|
|||||
| doc | Our Documentation | Python.org | 200 | 522 | 8 | Needs Attention |
|
|||||
| doc/av | Audio/Video Instructional Materials for Python... | 200 | 901 | 8 | Needs Attention |
|
|||||
| download/alternatives | Alternative Python implementations | Python.org | 200 | 571 | 8 | Needs Attention |
|
|||||
| downloads/macos | Python Releases for macOS | Python.org | 200 | 4861 | 8 | Needs Attention |
|
|||||
| downloads/source | Python Source Releases | Python.org | 200 | 7512 | 8 | Needs Attention |
|
|||||
| downloads/windows | Python Releases for Windows | Python.org | 200 | 14282 | 8 | Needs Attention |
|
|||||
| events/calendars | Python Calendars | Python.org | 200 | 324 | 8 | Needs Attention |
|
|||||
| events/python-events/2172 | FastAPI Conf 2026 | Python.org | 200 | 372 | 8 | Needs Attention |
|
|||||
| jobs/type/big-data | Python Job Board | Python.org | 200 | 465 | 8 | Needs Attention |
|
|||||
| jobs/type/cloud | Python Job Board | Python.org | 200 | 651 | 8 | Needs Attention |
|
|||||
| jobs/type/database | Python Job Board | Python.org | 200 | 558 | 8 | Needs Attention |
|
|||||
| jobs/type/finance | Python Job Board | Python.org | 200 | 458 | 8 | Needs Attention |
|
|||||
| jobs/type/front-end | Python Job Board | Python.org | 200 | 596 | 8 | Needs Attention |
|
|||||
| jobs/type/integration | Python Job Board | Python.org | 200 | 580 | 8 | Needs Attention |
|
|||||
| jobs/type/lead | Python Job Board | Python.org | 200 | 453 | 8 | Needs Attention |
|
|||||
| jobs/type/machine-learning | Python Job Board | Python.org | 200 | 664 | 8 | Needs Attention |
|
|||||
| jobs/type/management | Python Job Board | Python.org | 200 | 453 | 8 | Needs Attention |
|
|||||
| nominations/elections | Elections | Python.org | 200 | 1151 | 8 | Needs Attention |
|
|||||
| psf/annual-report/2024 | 2024 PSF Annual Impact Report | Python... | 200 | 483 | 8 | Needs Attention |
|
|||||
| psf/board | PSF Officers & Board Members | Python Software... | 200 | 3236 | 8 | Needs Attention |
|
|||||
| psf/community-stories | Community Stories | Python Software Foundation | 200 | 1406 | 8 | At Risk |
|
|||||
| psf/developersinresidence | PSF Developers in Residence | Python.org | 200 | 1026 | 8 | Needs Attention |
|
|||||
| psf/get-involved | 👋 Hey Community Members! | Python Software Foundation | 200 | 677 | 8 | Needs Attention |
|
|||||
| psf/grants/faq | Grants - Frequently Asked Questions | Python... | 200 | 1525 | 8 | Needs Attention |
|
|||||
| psf/membership-faq | PSF Membership Types & FAQ | Python Software Foundation | 200 | 1372 | 8 | Needs Attention |
|
|||||
| psf/records | Python Software Foundation Public Records | Python.org | 200 | 633 | 8 | Needs Attention |
|
|||||
| success-stories/python-provides-convenience-and-flexibility-for-scalable-mlai | Python provides convenience and flexibility... | 200 | 443 | 8 | Needs Attention |
|
|||||
| downloads/android | Python Releases for Android | Python.org | 200 | 845 | 7 | Needs Attention |
|
|||||
| downloads/ios | Python Releases for iOS | Python.org | 200 | 417 | 7 | Needs Attention |
|
|||||
| jobs | Python Job Board | Python.org | 200 | 911 | 7 | Needs Attention |
|
|||||
| jobs/type/back-end | Python Job Board | Python.org | 200 | 871 | 7 | Needs Attention |
|
|||||
| psf/community-partners | PSF Community Partner Program | Python... | 200 | 1641 | 7 | Needs Attention |
|
|||||
| psf/donations/matching-gifts | Matching Donations | Python Software Foundation | 200 | 619 | 7 | Needs Attention |
|
|||||
| psf/fellows-roster | PSF Fellows Roster | Python Software Foundation | 200 | 2105 | 7 | Needs Attention |
|
|||||
| psf/grants | PSF Grants Program | Python Software Foundation | 200 | 4296 | 7 | Needs Attention |
|
|||||
| psf/meetup-pro | PSF Meetup Pro Network | Python Software Foundation | 200 | 935 | 7 | Needs Attention |
|
|||||
| psf/membership/supporting | Supporting Membership | Python Software Foundation | 200 | 842 | 7 | Needs Attention |
|
|||||
| psf/mission | Mission | Python Software Foundation | 200 | 877 | 7 | Needs Attention |
|
|||||
| success-stories | Our Success Stories | Python.org | 200 | 829 | 7 | At Risk |
|
|||||
| success-stories/category/arts | Arts | Our Success Stories | Python.org | 200 | 330 | 7 | Needs Attention |
|
|||||
| success-stories/category/business | Business | Our Success Stories | Python.org | 200 | 449 | 7 | Needs Attention |
|
|||||
| success-stories/category/education | Education | Our Success Stories | Python.org | 200 | 353 | 7 | Needs Attention |
|
|||||
| success-stories/category/engineering | Engineering | Our Success Stories | Python.org | 200 | 343 | 7 | Needs Attention |
|
|||||
| success-stories/category/government | Government | Our Success Stories | Python.org | 200 | 366 | 7 | Needs Attention |
|
|||||
| success-stories/category/scientific | Scientific | Our Success Stories | Python.org | 200 | 355 | 7 | Needs Attention |
|
|||||
| success-stories/category/software-development | Software Development | Our Success Stories | Python.org | 200 | 493 | 7 | Needs Attention |
|
|||||
| downloads/release/python-3151 | Python Release Python 3.15.1 | Python.org | 200 | 1120 | 6 | Needs Attention |
|
|||||
| psf/membership | Become a Member of the PSF | Python Software Foundation | 200 | 716 | 6 | Needs Attention |
|
|||||
| psf/sponsorship | Sponsor the PSF | Python Software Foundation | 200 | 939 | 6 | Needs Attention |
|
|||||
| psf/strategy | PSF Strategy | Python Software Foundation | 200 | 1253 | 6 | Needs Attention |
|
|||||
| psf | (no title) | 301 | 0 | 1 | Needs Attention |
|
|||||
| psf/conduct | (no title) | 302 | 0 | 1 | Needs Attention |
|
|||||
Shows how pages from python.org (Wayback Machine, December 2013) were mapped to pages on python.org (live today). Confidence scores indicate how certain the match is.
| Old URL | New URL | Confidence | Method | Status | SEO Changes | Live Check |
|---|---|---|---|---|---|---|
| /about/help | /about/help | 100% | Exact Path | Improved | 5 fields | Still live |
| /community | /community | 100% | Exact Path | Improved | 6 fields | Still live |
| / | / | 100% | Exact Path | Improved | 6 fields | Still live |
| /about | /about | 100% | Exact Path | Improved | 6 fields | Still live |
| /about/apps | /about/apps | 100% | Exact Path | Improved | 5 fields | Still live |
| /about/gettingstarted | /about/gettingstarted | 100% | Exact Path | Improved | 5 fields | Still live |
| /about/legal | /about/legal | 100% | Exact Path | Improved | 5 fields | Still live |
| /about/quotes | /about/quotes | 100% | Exact Path | Improved | 4 fields | Still live |
| /community/awards | /community/awards | 100% | Exact Path | Improved | 5 fields | -- |
| /community/diversity | /community/diversity | 100% | Exact Path | Improved | 5 fields | -- |
| /community/irc | /community/irc | 100% | Exact Path | Improved | 4 fields | -- |
| /community/jobs/index.html | /jobs/type/back-end | 100% | Title | Improved | 5 fields, 1 flag | To parent section, not the planned page |
| /community/lists | /community/lists | 100% | Exact Path | Improved | 5 fields | Still live |
| /community/logos | /community/logos | 100% | Exact Path | Improved | 6 fields | Still live |
| /community/sigs | /community/sigs | 100% | Exact Path | Improved | 4 fields | Still live |
| /community/jobs | /jobs | 85% | Slug | Improved | 5 fields, 1 flag | Still live, not the planned page |
| /community/pycon | /psf/volunteer/pycon | 85% | Slug | Improved | 6 fields, 1 flag | Still live, not the planned page |
| /community/sigs/current/distutils-sig/doc | /doc | 85% | Slug | Improved | 6 fields | Still live, not the planned page |
| /about/success | /success-stories | 82% | Title | Improved | 6 fields, 2 flags | Still live, not the planned page |
| /about/success/acqutek | /success-stories/category/arts | 78% | Title | Improved | 6 fields, 1 flag | Still live, not the planned page |
| /community/index.html | /dev/security | 77% | Title | Improved | 6 fields | Not found (404) |
| /about/success/strakt | /success-stories/category/software-development | 42% | Keyword | Improved | 6 fields, 1 flag | Still live, not the planned page |
| /community/jobs/howto | /jobs/type/lead | 42% | Keyword | Improved | 6 fields, 1 flag | Still live, not the planned page |
| /about/success/esr | /success-stories/category/business | 40% | Keyword | Improved | 6 fields, 1 flag | Still live, not the planned page |
| /about/success/guards | /success-stories/category/education | 40% | Keyword | Improved | 6 fields, 1 flag | Still live, not the planned page |
| /community/awards/psf-awards | /psf/sponsorship | 40% | Keyword | Improved | 6 fields, 1 flag | Still live, not the planned page |
| /about/success/astra | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/carmanah | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/honeywell | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/ilm | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/rackspace | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/merchandise | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /3kpoll | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /about/success/bats | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/cog | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/devil | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/devnet | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/dlink | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/enovad | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/ezro | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/forecastwatch | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/frequentis | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/gravityzoo | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/gusto | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/journyx | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/loveintros | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/mayavi | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/mmtk | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/natsworld | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/nexedi | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/philips | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/projectpipe | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/resolver | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/siena | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/st-andrews | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/superleague | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /about/success/suzanne | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/tempest | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/testgo | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/tribon | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/tttech | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/usa | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/verity | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/wingide | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/wordstream | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/success/xist | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /about/website | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /cgi-bin/psf/payment.py | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /community/awards/frank-willison | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/awards/frank-willison/2006-martelli | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/awards/psf-distinguished-awards | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/coordination | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/capi-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/catalog-sig | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /community/sigs/current/catalog-sig/others | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /community/sigs/current/catalog-sig/requirements | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /community/sigs/current/cplusplus-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/db-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/db-sig/status | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/distutils-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/distutils-sig/doc/requirements | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/distutils-sig/sig_charter | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /community/sigs/current/doc-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/doc-sig/otherlangs | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/doc-sig/stext | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/edu-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/edu-sig/old_page | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /community/sigs/current/email-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/i18n-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/image-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/image-sig/status | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/image-sig/t1lib | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/import-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/meta-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/pythonmac-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/stdlib-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/uls-sig | (no match) | 0% | Unmatched | Missing | -- | Not found (404) |
| /community/sigs/current/web-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| /community/sigs/current/xml-sig | (no match) | 0% | Unmatched | Missing | -- | Live redirect |
| -- | /psf | -- | New Content | New Content | -- | -- |
| -- | /psf-landing | -- | New Content | New Content | -- | -- |
| -- | /downloads | -- | New Content | New Content | -- | -- |
| -- | /downloads/source | -- | New Content | New Content | -- | -- |
| -- | /downloads/windows | -- | New Content | New Content | -- | -- |
| -- | /downloads/macos | -- | New Content | New Content | -- | -- |
| -- | /downloads/android | -- | New Content | New Content | -- | -- |
| -- | /downloads/ios | -- | New Content | New Content | -- | -- |
| -- | /download/other | -- | New Content | New Content | -- | -- |
| -- | /download/alternatives | -- | New Content | New Content | -- | -- |
| -- | /doc/av | -- | New Content | New Content | -- | -- |
| -- | /doc/essays | -- | New Content | New Content | -- | -- |
| -- | /community/forums | -- | New Content | New Content | -- | -- |
| -- | /psf/annual-report/2024 | -- | New Content | New Content | -- | -- |
| -- | /community/workshops | -- | New Content | New Content | -- | -- |
| -- | /psf/conduct | -- | New Content | New Content | -- | -- |
| -- | /psf/get-involved | -- | New Content | New Content | -- | -- |
| -- | /psf/community-stories | -- | New Content | New Content | -- | -- |
| -- | /success-stories/category/engineering | -- | New Content | New Content | -- | -- |
| -- | /success-stories/category/government | -- | New Content | New Content | -- | -- |
| -- | /success-stories/category/scientific | -- | New Content | New Content | -- | -- |
| -- | /blogs | -- | New Content | New Content | -- | -- |
| -- | /psf/newsletter | -- | New Content | New Content | -- | -- |
| -- | /events | -- | New Content | New Content | -- | -- |
| -- | /events/python-events | -- | New Content | New Content | -- | -- |
| -- | /events/python-user-group | -- | New Content | New Content | -- | -- |
| -- | /events/python-events/past | -- | New Content | New Content | -- | -- |
| -- | /events/python-user-group/past | -- | New Content | New Content | -- | -- |
| -- | /shell | -- | New Content | New Content | -- | -- |
| -- | /downloads/release/python-3151 | -- | New Content | New Content | -- | -- |
| -- | /events/calendars | -- | New Content | New Content | -- | -- |
| -- | /events/python-events/2180 | -- | New Content | New Content | -- | -- |
| -- | /events/python-events/2172 | -- | New Content | New Content | -- | -- |
| -- | /events/python-events/2188 | -- | New Content | New Content | -- | -- |
| -- | /events/python-events/2150 | -- | New Content | New Content | -- | -- |
| -- | /events/python-user-group/2249 | -- | New Content | New Content | -- | -- |
| -- | /success-stories/python-provides-convenience-and-flexibility-for-scalable-mlai | -- | New Content | New Content | -- | -- |
| -- | /psf/membership | -- | New Content | New Content | -- | -- |
| -- | /psf/donations | -- | New Content | New Content | -- | -- |
| -- | /dev | -- | New Content | New Content | -- | -- |
| -- | /dev/core-mentorship | -- | New Content | New Content | -- | -- |
| -- | /psf/about | -- | New Content | New Content | -- | -- |
| -- | /psf/mission | -- | New Content | New Content | -- | -- |
| -- | /psf/board | -- | New Content | New Content | -- | -- |
| -- | /psf/strategy | -- | New Content | New Content | -- | -- |
| -- | /psf/records/staff | -- | New Content | New Content | -- | -- |
| -- | /psf/fiscal-sponsorees | -- | New Content | New Content | -- | -- |
| -- | /psf/records | -- | New Content | New Content | -- | -- |
| -- | /psf/about/legal-and-policies | -- | New Content | New Content | -- | -- |
| -- | /psf/faq | -- | New Content | New Content | -- | -- |
| -- | /psf/developersinresidence | -- | New Content | New Content | -- | -- |
| -- | /psf/sponsors | -- | New Content | New Content | -- | -- |
| -- | /sponsors/application | -- | New Content | New Content | -- | -- |
| -- | /psf/prospectus2026 | -- | New Content | New Content | -- | -- |
| -- | /psf/membership-faq | -- | New Content | New Content | -- | -- |
| -- | /nominations/elections | -- | New Content | New Content | -- | -- |
| -- | /psf/fellows-roster | -- | New Content | New Content | -- | -- |
| -- | /psf/membership/supporting | -- | New Content | New Content | -- | -- |
| -- | /psf/donations/matching-gifts | -- | New Content | New Content | -- | -- |
| -- | /psf/volunteer | -- | New Content | New Content | -- | -- |
| -- | /psf/workgroups | -- | New Content | New Content | -- | -- |
| -- | /psf/grants | -- | New Content | New Content | -- | -- |
| -- | /psf/grants/faq | -- | New Content | New Content | -- | -- |
| -- | /psf/community-partners | -- | New Content | New Content | -- | -- |
| -- | /psf/meetup-pro | -- | New Content | New Content | -- | -- |
| -- | /psf/news-and-community | -- | New Content | New Content | -- | -- |
| -- | /jobs/types | -- | New Content | New Content | -- | -- |
| -- | /jobs/type/big-data | -- | New Content | New Content | -- | -- |
| -- | /jobs/type/cloud | -- | New Content | New Content | -- | -- |
| -- | /jobs/type/database | -- | New Content | New Content | -- | -- |
| -- | /jobs/type/finance | -- | New Content | New Content | -- | -- |
| -- | /jobs/type/front-end | -- | New Content | New Content | -- | -- |
| -- | /jobs/type/integration | -- | New Content | New Content | -- | -- |
| -- | /jobs/type/machine-learning | -- | New Content | New Content | -- | -- |
| -- | /jobs/type/management | -- | New Content | New Content | -- | -- |
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 (74) are listed in Missing Pages.
| Signal | Kept | Changed | Added | Lost | Not comparable | Coverage before -> after |
|---|---|---|---|---|---|---|
| Title | 10 | 11 | 0 | 0 | 0 | 21 -> 21 present of 21 |
| Meta description | 0 | 21 | 0 | 0 | 0 | 21 -> 21 present of 21 |
| H1 | 5 | 10 | 5 | 1 | 0 | 16 -> 20 present of 21 |
| Section headings | 0 | 17 | 3 | 1 | 0 | 18 -> 20 present of 21 |
| Canonical | 0 | 0 | 0 | 0 | 0 | 0 -> 0 present of 21 |
| Indexability | 21 | 0 | 0 | 0 | 0 | 21 -> 21 indexable of 21 |
| Robots directives | 0 | 0 | 0 | 0 | 0 | 0 -> 0 present of 21 |
| Structured data | 0 | 0 | 21 | 0 | 0 | 0 -> 21 present of 21 |
| Social tags | 0 | 0 | 21 | 0 | 0 | 0 -> 21 present of 21 |
| hreflang | 0 | 0 | 0 | 0 | 0 | 0 -> 0 present of 21 |
| Language | 21 | 0 | 0 | 0 | 0 | 21 -> 21 present of 21 |
Counts cover the 21 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.
Plus 5 flags on low-confidence pairs (hidden).
Click a row to see the Before | After card. Flagged pairs come first.
| Old URL -> New URL | Match | Similarity | Fields changed | Flags |
|---|---|---|---|---|
| /about/success/ -> /success-stories/ | 82% Title | 44% | 6 | 2 Recommended |
|
http://python.org/about/success/ -> https://python.org/success-stories/
Old page: Archive copy from 2013-11-27
Title
Changed83% similar
Before
After
added: Our Success Storiesadded: | Python.org Words no longer in the title or the H1: python.
Meta description
Changed24% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Lost
Before
After
(none) H1 count: 1 -> 0.
Section headings
Changed
Before
H2
H3
After
H2
H3
-87 / +15 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 2,193 -> 829 (-62%)
Internal links: 60 -> 81 (+35%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/success/acqutek/ -> /success-stories/category/arts/ | 78% Title | 35% | 6 | 1 Recommended |
|
http://www.python.org/about/success/acqutek/ -> https://python.org/success-stories/category/arts/
Old page: Archive copy from 2013-11-22
Title
Changed75% similar
Before
After
added: Arts | Our Success Storiesadded: | Python.org Words no longer in the title or the H1: python.
Meta description
Changed24% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Changed7% similar
Before
After
added: Arts
Section headings
Lost
Before
H2
H3 (none)
After
H2 (none)
H3 (none)
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 1,340 -> 330 (-75%)
Internal links: 26 -> 54 (+108%)
Images: 13 -> 1 (-92%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/success/esr/ -> /success-stories/category/business/ | 40% Keyword low confidence | 29% | 6 | 1 Recommended |
|
http://www.python.org/about/success/esr/ -> https://python.org/success-stories/category/business/
Old page: Archive copy from 2013-11-22
Title
Changed65% similar
Before
After
added: Business | Our Success Storiesadded: | Python.org Words no longer in the title or the H1: python.
Meta description
Changed24% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Changed10% similar
Before
After
added: Business
Section headings
Lost
Before
H2
H3 (none)
After
H2 (none)
H3 (none)
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 3,585 -> 449 (-87%)
Internal links: 18 -> 69 (+283%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/success/guards/ -> /success-stories/category/education/ | 40% Keyword low confidence | 36% | 6 | 1 Recommended |
|
http://www.python.org/about/success/guards/ -> https://python.org/success-stories/category/education/
Old page: Archive copy from 2013-11-08
Title
Changed72% similar
Before
After
added: Education | Our Success Storiesadded: | Python.org Words no longer in the title or the H1: python.
Meta description
Changed24% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Changed25% similar
Before
After
added: Education
Section headings
Lost
Before
H2
H3 (none)
After
H2 (none)
H3 (none)
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 966 -> 353 (-63%)
Internal links: 20 -> 57 (+185%)
Images: 8 -> 1 (-88%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/success/strakt/ -> /success-stories/category/software-development/ | 42% Keyword low confidence | 29% | 6 | 1 Recommended |
|
http://www.python.org/about/success/strakt/ -> https://python.org/success-stories/category/software-development/
Old page: Archive copy from 2013-11-22
Title
Changed59% similar
Before
After
added: Software Development | Our Success Storiesadded: | Python.org Words no longer in the title or the H1: python.
Meta description
Changed24% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Changed43% similar
Before
After
added: Software Development
Section headings
Lost
Before
H2
H3 (none)
After
H2 (none)
H3 (none)
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 1,782 -> 493 (-72%)
Internal links: 21 -> 76 (+262%)
Images: 7 -> 1 (-86%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/awards/psf-awards/ -> /psf/sponsorship/ | 40% Keyword low confidence | 21% | 6 | 1 Recommended |
|
http://www.python.org/community/awards/psf-awards/ -> https://python.org/psf/sponsorship/
Old page: Archive copy from 2013-11-05
Title
Changed33% similar
Before
PSF After
added: Sponsor the PSF added: | Python Software Foundation Words no longer in the title or the H1: awards, community, service.
Meta description
Changed18% similar
Before
After
added: The official home of the Python Programming Language
H1
Changed57% similar
Before
Python Software Foundation After
added: The Python Software Foundation added: Sponsorship Program
Section headings
Changed
Before
H2
H3 (none)
After
H2
H3 (none)
-18 / +3 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 2,339 -> 939 (-60%)
Internal links: 25 -> 82 (+228%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/jobs/howto/ -> /jobs/type/lead/ | 42% Keyword low confidence | 35% | 6 | 1 Recommended |
|
http://www.python.org/community/jobs/howto/ -> https://python.org/jobs/type/lead/
Old page: Archive copy from 2013-11-17
Title
Changed60% similar
Before
After
Python Job Boardadded: | Python.org Words no longer in the title or the H1: submit. The new title is used by 11 pages.
Meta description
Changed43% similar
Before
After
added: The official home of the Python added: Programming Language
H1
Changed52% similar
Before
After
added: 1 Python added: job added: in Lead
Section headings
Added
Before
H2 (none)
H3 (none)
After
H2
H3
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 815 -> 453 (-44%)
Internal links: 21 -> 93 (+343%)
Images: 4 -> 19 (+375%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/pycon/ -> /psf/volunteer/pycon/ | 85% Slug | 24% | 6 | 1 Recommended |
|
http://www.python.org/community/pycon/ -> https://python.org/psf/volunteer/pycon/
Old page: Archive copy from 2013-11-30
Title
Changed36% similar
Before
PyCon After
added: Volunteer Opportunities for PyCon added: US | Python Software Foundation
Meta description
Changed47% similar
Before
After
added: The official added: home added: of the Python Programming Language
H1
Changed19% similar
Before
After
added: Volunteer Opportunities for PyCon US H1 count: 1 -> 2.
Section headings
Added
Before
H2 (none)
H3 (none)
After
H2 (none)
H3
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 237 -> 499 (+111%)
Internal links: 22 -> 82 (+273%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/jobs/ -> /jobs/ | 85% Slug | 41% | 5 | 1 Recommended |
|
http://www.python.org/community/jobs/ -> https://python.org/jobs/
Old page: Archive copy from 2013-11-27
Meta description
Changed29% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Changed68% similar
Before
Python Job Board After
added: 19 jobs on the Python Job Board
Section headings
Changed
Before
H2
H3 (none)
After
H2
H3
-127 / +23 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
On neither page: Canonical, Robots directives, hreflang.
Word count: 25,812 -> 911 (-96%)
Internal links: 23 -> 111 (+383%)
Images: 4 -> 19 (+375%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/jobs/index.html -> /jobs/type/back-end/ | 100% Title | 41% | 5 | 1 Recommended |
|
http://www.python.org/community/jobs/index.html -> https://python.org/jobs/type/back-end/
Old page: Archive copy from 2013-11-27
Meta description
Changed29% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Changed67% similar
Before
Python After
added: 17 Python added: jobs in Back end
Section headings
Changed
Before
H2
H3 (none)
After
H2
H3
-127 / +21 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
On neither page: Canonical, Robots directives, hreflang.
Word count: 25,812 -> 871 (-97%)
Internal links: 23 -> 109 (+374%)
Images: 4 -> 19 (+375%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| / -> / | 100% Exact Path | 21% | 6 | Changed |
|
http://www.python.org/ -> https://python.org/
Old page: Archive copy from 2013-11-27
Title
Changed24% similar
Before
After
added: Welcome to Python.org Words no longer in the title or the H1: language, official, programming, website.
Meta description
Changed26% similar
Before
After
added: The official added: home added: of the Python added: Programming added: Language
H1
Changed22% similar
Before
After
added: Functions Defined H1 count: 1 -> 5.
Section headings
Changed
Before
H2
H3 (none)
After
H2
H3 (none)
-7 / +9 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 614 -> 1,101 (+79%)
Internal links: 35 -> 64 (+83%)
Images: 5 -> 1 (-80%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/ -> /about/ | 100% Exact Path | 41% | 6 | Changed |
|
http://www.python.org/about/ -> https://python.org/about/
Old page: Archive copy from 2013-11-30
Title
Changed53% similar
Before
About After
Aboutadded: Pythonâ„¢ | Python.org
Meta description
Changed10% similar
Before
After
added: The official home of the Python Programming Language
H1
Changed10% similar
Before
After
Pythonadded: is powerful... and fast;plays well with others;runs everywhere;is friendly & easy to learn;is Open.
Section headings
Changed
Before
H2
H3 (none)
After
H2
H3 (none)
-5 / +7 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 680 -> 666 (about the same)
Internal links: 24 -> 62 (+158%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/ -> /community/ | 100% Exact Path | 38% | 6 | Changed |
|
http://python.org/community/ -> https://python.org/community/
Old page: Archive copy from 2013-11-27
Title
Changed76% similar
Before
After
added: Our Communityadded: | Python.org
Meta description
Changed32% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Added
Before
(none) After
added: Python’s community is vast;diverse & aims to grow;Python is Open. H1 count: 0 -> 1.
Section headings
Changed
Before
H2
H3 (none)
After
H2
H3 (none)
-2 / +8 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 226 -> 605 (+168%)
Internal links: 28 -> 53 (+89%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/index.html -> /dev/security/ | 77% Title | 36% | 6 | Changed |
|
http://www.python.org/community/index.html -> https://python.org/dev/security/
Old page: Archive copy from 2013-04-03 242 days from the target date
Title
Changed77% similar
Before
Python After
Python added: Security | Python.org Words no longer in the title or the H1: community.
Meta description
Changed32% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Added
Before
(none) After
added: Python Security H1 count: 0 -> 5.
Section headings
Changed
Before
H2
H3 (none)
After
H2
H3
-2 / +3 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 226 -> 817 (+262%)
Internal links: 28 -> 53 (+89%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/logos/ -> /community/logos/ | 100% Exact Path | 31% | 6 | Changed |
|
http://www.python.org/community/logos/ -> https://python.org/community/logos/
Old page: Archive copy from 2013-11-04
Title
Changed51% similar
Before
The Python Logo After
The Python Logoadded: | Python Software Foundation
Meta description
Changed24% similar
Before
After
added: Inline image sizing
H1
Added
Before
(none) After
added: The Python Logo H1 count: 0 -> 5.
Section headings
Changed
Before
H2
H3 (none)
After
H2 (none)
H3
-4 / +1 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 379 -> 695 (+83%)
Internal links: 38 -> 98 (+158%)
Images: 7 -> 5 (-29%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/sigs/current/distutils-sig/doc/ -> /doc/ | 85% Slug | 41% | 6 | Changed |
|
http://www.python.org/community/sigs/current/distutils-sig/doc/ -> https://python.org/doc/
Old page: Archive copy from 2013-09-21
Title
Changed62% similar
Before
After
added: Our Documentationadded: | Python.org Words no longer in the title or the H1: distutils, python.
Meta description
Changed25% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Changed18% similar
Before
After
added: Browse the docs online or download a copy of your own.
Section headings
Changed
Before
H2
H3 (none)
After
H2
H3 (none)
-3 / +7 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 436 -> 522 (+20%)
Internal links: 37 -> 54 (+46%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/apps/ -> /about/apps/ | 100% Exact Path | 54% | 5 | Changed |
|
http://www.python.org/about/apps/ -> https://python.org/about/apps/
Old page: Archive copy from 2013-11-27
Meta description
Changed29% similar
Before
After
added: The official home of the Pythonadded: Programming Language
H1
Changed67% similar
Before
After
added: Applications for Python H1 count: 1 -> 7.
Section headings
Changed
Before
H2
H3 (none)
After
H2 (none)
H3
-8 / +1 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
On neither page: Canonical, Robots directives, hreflang.
Word count: 536 -> 743 (+39%)
Internal links: 20 -> 53 (+165%)
Images: 5 -> 1 (-80%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/gettingstarted/ -> /about/gettingstarted/ | 100% Exact Path | 54% | 5 | Changed |
|
http://www.python.org/about/gettingstarted/ -> https://python.org/about/gettingstarted/
Old page: Archive copy from 2013-11-30
Meta description
Changed36% similar
Before
Python After
added: The official home of the Python added: Programming Language
H1
Changed26% similar
Before
After
Pythonadded: For Beginners H1 count: 1 -> 6.
Section headings
Changed
Before
H2
H3 (none)
After
H2 (none)
H3
-5 / +1 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
On neither page: Canonical, Robots directives, hreflang.
Word count: 552 -> 805 (+46%)
Internal links: 21 -> 54 (+157%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/help/ -> /about/help/ | 100% Exact Path | 54% | 5 | Changed |
|
http://python.org/about/help/ -> https://python.org/about/help/
Old page: Archive copy from 2013-11-27
Meta description
Changed14% similar
Before
After
added: The official home of the Python Programming Language
H1
Changed15% similar
Before
After
added: Help H1 count: 1 -> 10.
Section headings
Changed
Before
H2
H3 (none)
After
H2 (none)
H3
-7 / +1 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
On neither page: Canonical, Robots directives, hreflang.
Word count: 518 -> 729 (+41%)
Internal links: 27 -> 54 (+100%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/legal/ -> /about/legal/ | 100% Exact Path | 32% | 5 | Changed |
|
http://www.python.org/about/legal/ -> https://python.org/about/legal/
Old page: Archive copy from 2013-11-17
Title
Changed52% similar
Before
Legal Statements After
Legal Statementsadded: | Python Software Foundation
Meta description
Changed21% similar
Before
After
added: The official home of the Python Programming Language
Section headings
Added
Before
H2 (none)
H3 (none)
After
H2 (none)
H3
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: H1, Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 410 -> 716 (+75%)
Internal links: 20 -> 84 (+320%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/awards/ -> /community/awards/ | 100% Exact Path | 32% | 5 | Changed |
|
http://www.python.org/community/awards/ -> https://python.org/community/awards/
Old page: Archive copy from 2013-11-08
Title
Changed61% similar
Before
Python Community Awards After
Python Community Awardsadded: | Python Software Foundation
Meta description
Changed32% similar
Before
Python After
added: The official home of the Python added: Programming Language
Section headings
Added
Before
H2 (none)
H3 (none)
After
H2 (none)
H3
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: H1, Indexability, Language.
On neither page: Canonical, Robots directives, hreflang.
Word count: 171 -> 429 (+151%)
Internal links: 24 -> 84 (+250%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/diversity/ -> /community/diversity/ | 100% Exact Path | 52% | 5 | Changed |
|
http://www.python.org/community/diversity/ -> https://python.org/community/diversity/
Old page: Archive copy from 2013-11-04
Meta description
Changed13% similar
Before
After
added: The official home of the Python Programming Language
H1
Added
Before
(none) After
added: Diversity H1 count: 0 -> 3.
Section headings
Changed
Before
H2
H3 (none)
After
H2 (none)
H3
-2 / +1 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
On neither page: Canonical, Robots directives, hreflang.
Word count: 347 -> 565 (+63%)
Internal links: 21 -> 52 (+148%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/lists/ -> /community/lists/ | 100% Exact Path | 57% | 5 | Changed |
|
http://www.python.org/community/lists/ -> https://python.org/community/lists/
Old page: Archive copy from 2013-11-04
Meta description
Changed22% similar
Before
After
added: The official home of the Python Programming Language
H1
Added
Before
(none) After
added: Mailing lists H1 count: 0 -> 11.
Section headings
Changed
Before
H2
H3 (none)
After
H2 (none)
H3
-11 / +1 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
On neither page: Canonical, Robots directives, hreflang.
Word count: 1,218 -> 1,419 (+17%)
Internal links: 24 -> 54 (+125%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /about/quotes/ -> /about/quotes/ | 100% Exact Path | 55% | 4 | Changed |
|
http://www.python.org/about/quotes/ -> https://python.org/about/quotes/
Old page: Archive copy from 2013-11-27
Meta description
Changed28% similar
Before
After
added: The official home of the Pythonadded: Programming Language
Section headings
Changed
Before
H2
H3 (none)
After
H2 (none)
H3
-11 / +1 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
H1 kept: H1 count: 1 -> 13.
On neither page: Canonical, Robots directives, hreflang.
Word count: 977 -> 1,293 (+32%)
Internal links: 18 -> 52 (+189%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/irc/ -> /community/irc/ | 100% Exact Path | 52% | 4 | Changed |
|
http://www.python.org/community/irc/ -> https://python.org/community/irc/
Old page: Archive copy from 2013-11-04
Meta description
Changed17% similar
Before
After
added: The official home of the Python Programming Language
Section headings
Changed
Before
H2
H3 (none)
After
H2 (none)
H3
-2 / +1 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
H1 kept: H1 count: 1 -> 3.
On neither page: Canonical, Robots directives, hreflang.
Word count: 318 -> 547 (+72%)
Internal links: 21 -> 52 (+148%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
| /community/sigs/ -> /community/sigs/ | 100% Exact Path | 53% | 4 | Changed |
|
http://www.python.org/community/sigs/ -> https://python.org/community/sigs/
Old page: Archive copy from 2013-11-27
Meta description
Changed29% similar
Before
Python After
added: The official home of the Python added: Programming Language
Section headings
Changed
Before
H2
H3 (none)
After
H2 (none)
H3
-4 / +1 headings.
Structured data
Added
Before
(none) After
added: WebSite
Social tags
Added
Before
(none) After
added: og:titleadded: og:descriptionadded: og:imageadded: og:urladded: og:type Kept: Indexability, Language.
Title kept: Only a brand suffix was added.
H1 kept: H1 count: 1 -> 5.
On neither page: Canonical, Robots directives, hreflang.
Word count: 507 -> 765 (+51%)
Internal links: 43 -> 70 (+63%)
Images: 4 -> 1 (-75%)
Images missing alt: 1 -> 0 (-100%)
|
||||
These pages from python.org (Wayback Machine, December 2013) were not found on python.org (live today). The migration team may want to consider rebuilding these pages or setting up redirects to the most relevant new page.
Lost pages by type: Content Page (74)
| Old URL | Title | Words | Original Health | Loss Category | Live Today | Suggested Fix |
|---|---|---|---|---|---|---|
| about/success/astra | Python Success Stories | 2489 | Needs Attention | Content Page | Still live | No action |
| about/success/carmanah | Python Success Stories | 1973 | Needs Attention | Content Page | Still live | No action |
| about/success/honeywell | Python Success Stories | 2364 | Needs Attention | Content Page | Still live | No action |
| about/success/ilm | Python Success Stories | 1705 | Needs Attention | Content Page | Still live | No action |
| about/success/rackspace | Python Success Stories | 1874 | Needs Attention | Content Page | Still live | No action |
| community/merchandise | Python Merchandise | 252 | Needs Attention | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| 3kpoll | Poll results | 235 | At Risk | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| about/success/bats | Python Success Stories | 2005 | Needs Attention | Content Page | Still live | No action |
| about/success/cog | Python Success Stories | 1631 | Needs Attention | Content Page | Still live | No action |
| about/success/devil | Python Success Stories | 1905 | Needs Attention | Content Page | Still live | No action |
| about/success/devnet | Python Success Stories | 742 | Needs Attention | Content Page | Still live | No action |
| about/success/dlink | python.org | 920 | Needs Attention | Content Page | Still live | No action |
| about/success/enovad | Python Success Stories | 1026 | Needs Attention | Content Page | Still live | No action |
| about/success/ezro | Python Success Stories | 1389 | Needs Attention | Content Page | Still live | No action |
| about/success/forecastwatch | Python Success Stories | 1372 | Needs Attention | Content Page | Still live | No action |
| about/success/frequentis | Python Success Stories | 1147 | Needs Attention | Content Page | Still live | No action |
| about/success/gravityzoo | Python Success Stories | 1283 | Needs Attention | Content Page | Still live | No action |
| about/success/gusto | Python Success Stories | 1597 | Needs Attention | Content Page | Still live | No action |
| about/success/journyx | Python Success Stories | 1103 | Needs Attention | Content Page | Still live | No action |
| about/success/loveintros | Python Success Stories | 977 | Needs Attention | Content Page | Still live | No action |
| about/success/mayavi | Python Success Stories | 1315 | Needs Attention | Content Page | Still live | No action |
| about/success/mmtk | Python Success Stories | 1030 | Needs Attention | Content Page | Still live | No action |
| about/success/natsworld | Python Success Stories | 1581 | Needs Attention | Content Page | Still live | No action |
| about/success/nexedi | Python Success Stories | 2143 | Needs Attention | Content Page | Still live | No action |
| about/success/philips | Python Success Stories | 1644 | Needs Attention | Content Page | Still live | No action |
| about/success/projectpipe | Python Success Stories | 1700 | Needs Attention | Content Page | Still live | No action |
| about/success/resolver | Python Success Stories | 2900 | Needs Attention | Content Page | Still live | No action |
| about/success/siena | Python Success Stories | 1461 | Needs Attention | Content Page | Still live | No action |
| about/success/st-andrews | Python Success Stories | 1039 | Needs Attention | Content Page | Still live | No action |
| about/success/superleague | Index of /about/success/superleague | 18 | At Risk | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| about/success/suzanne | Python Success Stories | 1180 | Needs Attention | Content Page | Still live | No action |
| about/success/tempest | Python Success Stories | 1083 | Needs Attention | Content Page | Still live | No action |
| about/success/testgo | Python Success Stories | 676 | Needs Attention | Content Page | Still live | No action |
| about/success/tribon | Python Success Stories | 1129 | Needs Attention | Content Page | Still live | No action |
| about/success/tttech | Python Success Stories | 1126 | Needs Attention | Content Page | Still live | No action |
| about/success/usa | Python Success Stories | 1345 | Needs Attention | Content Page | Still live | No action |
| about/success/verity | Python Success Stories | 1177 | Needs Attention | Content Page | Still live | No action |
| about/success/wingide | Python Success Stories | 2376 | Needs Attention | Content Page | Still live | No action |
| about/success/wordstream | Python Success Stories | 930 | Needs Attention | Content Page | Still live | No action |
| about/success/xist | Python Success Stories | 1234 | Needs Attention | Content Page | Still live | No action |
| about/website | About the Python Web Site | 212 | Needs Attention | Content Page | Still live | No action |
| cgi-bin/psf/payment.py | PSF Donation - Input Errors | 102 | At Risk | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| community/awards/frank-willison | Frank Willison Memorial Award | 1605 | Needs Attention | Content Page | Still live | No action |
| community/awards/frank-willison/2006-martelli | A Journey to Python | 1459 | Needs Attention | Content Page | Still live | No action |
| community/awards/psf-distinguished-awards | PSF Distinguished Service Awards | 451 | Needs Attention | Content Page | Still live | No action |
| community/sigs/coordination | Python Special Interest Groups - Coordinator... | 288 | Needs Attention | Content Page | Still live | No action |
| community/sigs/current | Python Special Interest Groups | 261 | At Risk | Content Page | Still live | No action |
| community/sigs/current/capi-sig | SIG for Supporting Use of the Python/C API | 143 | At Risk | Content Page | Still live | No action |
| community/sigs/current/catalog-sig | SIG for Python Resource Cataloguing | 324 | At Risk | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| community/sigs/current/catalog-sig/others | Other Catalog Systems | 193 | At Risk | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| community/sigs/current/catalog-sig/requirements | Catalog Requirements | 595 | At Risk | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| community/sigs/current/cplusplus-sig | SIG for development of Python/C++ integration | 1149 | At Risk | Content Page | Still live | No action |
| community/sigs/current/db-sig | SIG on Tabular Databases in Python | 157 | At Risk | Content Page | Still live | No action |
| community/sigs/current/db-sig/status | Python Tabular Databases SIG: Status | 168 | At Risk | Content Page | Still live | No action |
| community/sigs/current/distutils-sig | Python Distutils-SIG: Introduction | 291 | Needs Attention | Content Page | Still live | No action |
| community/sigs/current/distutils-sig/doc/requirements | Python Distutils-SIG: Requirements | 415 | Needs Attention | Content Page | Still live | No action |
| community/sigs/current/distutils-sig/sig_charter | Index of... | 18 | At Risk | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| community/sigs/current/doc-sig | Doc-SIG - Python Documentation Special Interest Group | 125 | Needs Attention | Content Page | Still live | No action |
| community/sigs/current/doc-sig/otherlangs | Other Documentation Tools | 743 | At Risk | Content Page | Still live | No action |
| community/sigs/current/doc-sig/stext | Structured Text Formatting Rules | 664 | At Risk | Content Page | Still live | No action |
| community/sigs/current/edu-sig | EDU-SIG: Python in Education | 3259 | At Risk | Content Page | Still live | No action |
| community/sigs/current/edu-sig/old_page | Index of /community/sigs/current/edu-sig/old_page | 18 | At Risk | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| community/sigs/current/email-sig | email package SIG | 319 | At Risk | Content Page | Still live | No action |
| community/sigs/current/i18n-sig | Python Internationalization-SIG | 946 | At Risk | Content Page | Still live | No action |
| community/sigs/current/image-sig | Image-SIG - Image Processing with Python SIG | 151 | At Risk | Content Page | Still live | No action |
| community/sigs/current/image-sig/status | Image Processing with Python SIG Status | 151 | At Risk | Content Page | Still live | No action |
| community/sigs/current/image-sig/t1lib | t1python - A Type1 Font Renderer for Python | 502 | Needs Attention | Content Page | Still live | No action |
| community/sigs/current/import-sig | Import Sig | 142 | At Risk | Content Page | Still live | No action |
| community/sigs/current/meta-sig | SIG on PSF SIGs and Mailing Lists | 147 | At Risk | Content Page | Still live | No action |
| community/sigs/current/pythonmac-sig | Pythonmac-SIG - SIG on Python for the Apple Macintosh | 204 | At Risk | Content Page | Still live | No action |
| community/sigs/current/stdlib-sig | SIG for Standard Library Development | 166 | Needs Attention | Content Page | Still live | No action |
| community/sigs/current/uls-sig | SIG for Ultra Large-Scale Systems | 336 | Needs Attention | Content Page | Not found (404) | Choose a target and add a 301, or return 410 if it was retired on purpose |
| community/sigs/current/web-sig | Web SIG | 441 | Needs Attention | Content Page | Still live | No action |
| community/sigs/current/xml-sig | SIG for XML Processing in Python | 249 | At Risk | Content Page | Still live | No action |
Webtrace requested 100 of 103 known old URLs (the top ones by estimated importance, URLs without a match first) and followed every redirect step.
Checked live on 2026-10-23 18:31 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.
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/merchandise/ Python Merchandise Content Page
|
Not found (404) | 301 -> 404 | /community/merchandise/ | -- | 48 | Choose a target and add a 301, or return 410 if it was retired on purpose | between 2022-11-14 and 2023-01-21 (became 404) (approx.) last 200 first change |
| 2 | /3kpoll Poll results Content Page
|
Not found (404) | 301 -> 404 | /3kpoll | -- | 26 | Choose a target and add a 301, or return 410 if it was retired on purpose | between 2013-12-30 and 2014-01-30 (became 404) (approx.) last 200 first change |
| 3 | /community/sigs/current/catalog-sig/ SIG for Python Resource Cataloguing Content Page
|
Not found (404) | 301 -> 404 | /community/sigs/current/catalog-sig/ | -- | 25 | Choose a target and add a 301, or return 410 if it was retired on purpose | between 2013-10-07 and 2014-07-31 (became 301) (approx.) last 200 first change |
| 4 | /community/sigs/current/uls-sig/ SIG for Ultra Large-Scale Systems Content Page
|
Not found (404) | 301 -> 404 | /community/sigs/current/uls-sig/ | -- | 25 | Choose a target and add a 301, or return 410 if it was retired on purpose | between 2014-08-16 and 2015-05-23 (became 301) (approx.) last 200 first change |
| 5 | /community/sigs/current/catalog-sig/requirements/ Catalog Requirements Content Page
|
Not found (404) | 301 -> 404 | /community/sigs/current/catalog-sig/requirements/ | -- | 21 | Choose a target and add a 301, or return 410 if it was retired on purpose | last seen 2013-03-16 (approx.) last 200 |
| 6 | /files/miller-dissertation.pdf miller-dissertation.pdf Document
|
Not found (404) | 301 -> 404 | /files/miller-dissertation.pdf | -- | 21 | Choose a target and add a 301, or return 410 if it was retired on purpose | between 2013-09-06 and 2014-03-31 (became 301) (approx.) last 200 first change |
| 7 | /about/success/superleague/ Index of /about/success/superleague Content Page
|
Not found (404) | 301 -> 404 | /about/success/superleague/ | -- | 16 | Choose a target and add a 301, or return 410 if it was retired on purpose | between 2014-02-05 and 2014-03-20 (became 301) (approx.) last 200 first change |
| 8 | /community/jobs/howto/job-template.txt job-template.txt Document
|
Not found (404) | 301 -> 404 | /community/jobs/howto/job-template.txt | -- | 11 | Choose a target and add a 301, or return 410 if it was retired on purpose | between 2014-01-26 and 2014-02-26 (became 301) (approx.) last 200 first change |
| 9 | /community/sigs/current/catalog-sig/others/ Other Catalog Systems Content Page
|
Not found (404) | 301 -> 404 | /community/sigs/current/catalog-sig/others/ | -- | 11 | Choose a target and add a 301, or return 410 if it was retired on purpose | last seen 2013-05-16 (approx.) last 200 |
| 10 | /cgi-bin/psf/payment.py PSF Donation - Input Errors Content Page
|
Not found (404) | 301 -> 404 | /cgi-bin/psf/payment.py | -- | 10 | Choose a target and add a 301, or return 410 if it was retired on purpose | last seen 2014-02-12 (approx.) last 200 |
| 11 | /community/index.html Python Community
|
Not found (404) | 301 -> 404 | /community/index.html | /dev/security/ | 10 | Add a 301 to /dev/security/ | between 2014-01-26 and 2014-02-26 (became 301) (approx.) last 200 first change |
| 12 | /community/sigs/current/distutils-sig/sig_charter/ Index of /community/sigs/current/distutils-sig/sig_charter Content Page
|
Not found (404) | 301 -> 404 | /community/sigs/current/distutils-sig/sig_charter/ | -- | 5 | Choose a target and add a 301, or return 410 if it was retired on purpose | last seen 2012-08-25 (approx.) last 200 |
| 13 | /community/sigs/current/edu-sig/old_page/ Index of /community/sigs/current/edu-sig/old_page Content Page
|
Not found (404) | 301 -> 404 | /community/sigs/current/edu-sig/old_page/ | -- | 5 | Choose a target and add a 301, or return 410 if it was retired on purpose | between 2012-05-31 and 2016-03-20 (became 301) (approx.) last 200 first change |
| 14 | /community/jobs/index.html Python Job Board
|
To parent section | 301 -> 301 -> 200 | /community/jobs/ Python Job Board | Python.org
|
/jobs/type/back-end/ | 15 | Add a 301 to /jobs/type/back-end/ | between 2014-02-06 and 2014-03-20 (became 301) (approx.) last 200 first change |
The fixes CSV lists every old URL above that needs attention. The .htaccess file holds 2 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)# 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 www.python.org --- # /community/index.html -> https://python.org/dev/security/ (Not found (404); live: 301 -> 404) RewriteRule ^community/index\.html$ /dev/security/ [R=301,L] # /community/jobs/index.html -> https://python.org/jobs/type/back-end/ (To parent section; live: 301 -> 301 -> 200) RewriteRule ^community/jobs/index\.html$ /jobs/type/back-end/ [R=301,L] # --- Old URLs without a suggested target (choose one, or return 410 if retired) --- # /community/merchandise (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /3kpoll (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /community/sigs/current/catalog-sig (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /community/sigs/current/uls-sig (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /community/sigs/current/catalog-sig/requirements (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /files/miller-dissertation.pdf (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /about/success/superleague (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /community/jobs/howto/job-template.txt (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /community/sigs/current/catalog-sig/others (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /cgi-bin/psf/payment.py (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /community/sigs/current/distutils-sig/sig_charter (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose # /community/sigs/current/edu-sig/old_page (Not found (404)): Choose a target and add a 301, or return 410 if it was retired on purpose
For 10 old URLs that no longer reach their 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.
| Period | Moved (3xx) | Gone (4xx/5xx) |
|---|---|---|
| Q1 2014 | 5 | 1 |
| Q3 2014 | 1 | 0 |
| Q2 2015 | 1 | 0 |
| Q1 2016 | 1 | 0 |
| Q1 2023 | 0 | 1 |
| Section | Checked | Reach their page | Reach a parent page | Lost | Not verified |
|---|---|---|---|---|---|
| /community/ | 45 | 35 | 1 | 9 | 0 |
| /about/ | 49 | 48 | 0 | 1 | 0 |
| / | 4 | 3 | 0 | 1 | 0 |
| /cgi-bin/ | 1 | 0 | 0 | 1 | 0 |
| /files/ | 1 | 0 | 0 | 1 | 0 |
| Old URL | Today | Hops | Lands on | Matches plan | Importance |
|---|---|---|---|---|---|
| /about/website/ | Still live | 301 -> 200 | /about/website/ | -- | 55 |
| /community/merchandise/ | Not found (404) | 301 -> 404 | /community/merchandise/ | -- | 48 |
| /community/sigs/coordination/ | Still live | 301 -> 200 | /community/sigs/coordination/ | -- | 39 |
| /community/sigs/current/ | Still live | 301 -> 200 | /community/sigs/current/ | -- | 39 |
| /community/awards/frank-willison/ | Still live | 301 -> 200 | /community/awards/frank-willison/ | -- | 34 |
| /community/awards/psf-distinguished-awards/ | Still live | 301 -> 200 | /community/awards/psf-distinguished-awards/ | -- | 34 |
| /community/sigs/current/edu-sig/ | Still live | 301 -> 200 | /community/sigs/current/edu-sig/ | -- | 31 |
| /about/success/astra/ | Still live | 301 -> 200 | /about/success/astra/ | -- | 30 |
| /about/success/honeywell/ | Still live | 301 -> 200 | /about/success/honeywell/ | -- | 30 |
| /about/success/ilm/ | Still live | 301 -> 200 | /about/success/ilm/ | -- | 30 |
| /about/success/rackspace/ | Still live | 301 -> 200 | /about/success/rackspace/ | -- | 30 |
| /about/success/mmtk/ | Still live | 301 -> 200 | /about/success/mmtk/ | -- | 30 |
| /about/success/natsworld/ | Still live | 301 -> 200 | /about/success/natsworld/ | -- | 30 |
| /about/success/carmanah/ | Still live | 301 -> 200 | /about/success/carmanah/ | -- | 26 |
| /3kpoll | Not found (404) | 301 -> 404 | /3kpoll | -- | 26 |
| /about/success/bats/ | Still live | 301 -> 200 | /about/success/bats/ | -- | 26 |
| /about/success/cog/ | Still live | 301 -> 200 | /about/success/cog/ | -- | 26 |
| /about/success/devil/ | Still live | 301 -> 200 | /about/success/devil/ | -- | 26 |
| /about/success/devnet/ | Still live | 301 -> 200 | /about/success/devnet/ | -- | 26 |
| /about/success/dlink/ | Still live | 301 -> 200 | /about/success/dlink/ | -- | 26 |
| /about/success/enovad/ | Still live | 301 -> 200 | /about/success/enovad/ | -- | 26 |
| /about/success/ezro/ | Still live | 301 -> 200 | /about/success/ezro/ | -- | 26 |
| /about/success/forecastwatch/ | Still live | 301 -> 200 | /about/success/forecastwatch/ | -- | 26 |
| /about/success/frequentis/ | Still live | 301 -> 200 | /about/success/frequentis/ | -- | 26 |
| /about/success/gravityzoo/ | Still live | 301 -> 200 | /about/success/gravityzoo/ | -- | 26 |
| /about/success/gusto/ | Still live | 301 -> 200 | /about/success/gusto/ | -- | 26 |
| /about/success/journyx/ | Still live | 301 -> 200 | /about/success/journyx/ | -- | 26 |
| /about/success/loveintros/ | Still live | 301 -> 200 | /about/success/loveintros/ | -- | 26 |
| /about/success/mayavi/ | Still live | 301 -> 200 | /about/success/mayavi/ | -- | 26 |
| /about/success/nexedi/ | Still live | 301 -> 200 | /about/success/nexedi/ | -- | 26 |
| /about/success/philips/ | Still live | 301 -> 200 | /about/success/philips/ | -- | 26 |
| /about/success/projectpipe/ | Still live | 301 -> 200 | /about/success/projectpipe/ | -- | 26 |
| /about/success/resolver/ | Still live | 301 -> 200 | /about/success/resolver/ | -- | 26 |
| /about/success/siena/ | Still live | 301 -> 200 | /about/success/siena/ | -- | 26 |
| /about/success/st-andrews/ | Still live | 301 -> 200 | /about/success/st-andrews/ | -- | 26 |
| /about/success/suzanne/ | Still live | 301 -> 200 | /about/success/suzanne/ | -- | 26 |
| /about/success/tempest/ | Still live | 301 -> 200 | /about/success/tempest/ | -- | 26 |
| /about/success/testgo/ | Still live | 301 -> 200 | /about/success/testgo/ | -- | 26 |
| /about/success/tribon/ | Still live | 301 -> 200 | /about/success/tribon/ | -- | 26 |
| /about/success/tttech/ | Still live | 301 -> 200 | /about/success/tttech/ | -- | 26 |
| /about/success/usa/ | Still live | 301 -> 200 | /about/success/usa/ | -- | 26 |
| /about/success/verity/ | Still live | 301 -> 200 | /about/success/verity/ | -- | 26 |
| /about/success/wingide/ | Still live | 301 -> 200 | /about/success/wingide/ | -- | 26 |
| /about/success/wordstream/ | Still live | 301 -> 200 | /about/success/wordstream/ | -- | 26 |
| /about/success/xist/ | Still live | 301 -> 200 | /about/success/xist/ | -- | 26 |
| /community/sigs/current/catalog-sig/ | Not found (404) | 301 -> 404 | /community/sigs/current/catalog-sig/ | -- | 25 |
| /community/sigs/current/cplusplus-sig/ | Still live | 301 -> 200 | /community/sigs/current/cplusplus-sig/ | -- | 25 |
| /community/sigs/current/email-sig/ | Still live | 301 -> 200 | /community/sigs/current/email-sig/ | -- | 25 |
| /community/sigs/current/i18n-sig/ | Still live | 301 -> 200 | /community/sigs/current/i18n-sig/ | -- | 25 |
| /community/sigs/current/uls-sig/ | Not found (404) | 301 -> 404 | /community/sigs/current/uls-sig/ | -- | 25 |
| /community/sigs/current/web-sig/ | Still live | 301 -> 200 | /community/sigs/current/web-sig/ | -- | 25 |
| /community/sigs/current/distutils-sig/ | Still live | 301 -> 200 | /community/sigs/current/distutils-sig/ | -- | 22 |
| /community/awards/frank-willison/2006-martelli/ | Still live | 301 -> 200 | /community/awards/frank-willison/2006-martelli/ | -- | 21 |
| /community/clpya-guidelines.txt | Still live | 301 -> 301 -> 200 | /community/clpya-guidelines.txt/ | -- | 21 |
| /community/sigs/current/catalog-sig/requirements/ | Not found (404) | 301 -> 404 | /community/sigs/current/catalog-sig/requirements/ | -- | 21 |
| /community/sigs/current/distutils-sig/doc/requirements/ | Still live | 301 -> 200 | /community/sigs/current/distutils-sig/doc/requirements/ | -- | 21 |
| /community/sigs/current/image-sig/t1lib/ | Still live | 301 -> 200 | /community/sigs/current/image-sig/t1lib/ | -- | 21 |
| /files/miller-dissertation.pdf | Not found (404) | 301 -> 404 | /files/miller-dissertation.pdf | -- | 21 |
| /community/sigs/current/doc-sig/ | Still live | 301 -> 200 | /community/sigs/current/doc-sig/ | -- | 19 |
| /community/sigs/current/image-sig/ | Still live | 301 -> 200 | /community/sigs/current/image-sig/ | -- | 19 |
| /community/sigs/current/db-sig/ | Still live | 301 -> 200 | /community/sigs/current/db-sig/ | -- | 17 |
| /about/success/superleague/ | Not found (404) | 301 -> 404 | /about/success/superleague/ | -- | 16 |
| /community/sigs/current/capi-sig/ | Still live | 301 -> 200 | /community/sigs/current/capi-sig/ | -- | 15 |
| /community/sigs/current/doc-sig/otherlangs/ | Still live | 301 -> 200 | /community/sigs/current/doc-sig/otherlangs/ | -- | 15 |
| /community/sigs/current/doc-sig/stext/ | Still live | 301 -> 200 | /community/sigs/current/doc-sig/stext/ | -- | 15 |
| /community/sigs/current/import-sig/ | Still live | 301 -> 200 | /community/sigs/current/import-sig/ | -- | 15 |
| /community/sigs/current/meta-sig/ | Still live | 301 -> 200 | /community/sigs/current/meta-sig/ | -- | 15 |
| /community/sigs/current/pythonmac-sig/ | Still live | 301 -> 200 | /community/sigs/current/pythonmac-sig/ | -- | 15 |
| /community/sigs/current/stdlib-sig/ | Still live | 301 -> 200 | /community/sigs/current/stdlib-sig/ | -- | 15 |
| /community/sigs/current/xml-sig/ | Still live | 301 -> 200 | /community/sigs/current/xml-sig/ | -- | 15 |
| /community/jobs/howto/job-template.txt | Not found (404) | 301 -> 404 | /community/jobs/howto/job-template.txt | -- | 11 |
| /community/sigs/current/catalog-sig/others/ | Not found (404) | 301 -> 404 | /community/sigs/current/catalog-sig/others/ | -- | 11 |
| /community/sigs/current/image-sig/status/ | Still live | 301 -> 200 | /community/sigs/current/image-sig/status/ | -- | 11 |
| /cgi-bin/psf/payment.py | Not found (404) | 301 -> 404 | /cgi-bin/psf/payment.py | -- | 10 |
| /community/sigs/current/db-sig/status/ | Still live | 301 -> 200 | /community/sigs/current/db-sig/status/ | -- | 5 |
| /community/sigs/current/distutils-sig/sig_charter/ | Not found (404) | 301 -> 404 | /community/sigs/current/distutils-sig/sig_charter/ | -- | 5 |
| /community/sigs/current/edu-sig/old_page/ | Not found (404) | 301 -> 404 | /community/sigs/current/edu-sig/old_page/ | -- | 5 |
| /about/success/ | Still live | 301 -> 200 | /about/success/ | No -- live: /about/success/; plan: /success-stories/ | 54 |
| /community/jobs/ | Still live | 301 -> 200 | /community/jobs/ | No -- live: /community/jobs/; plan: /jobs/ | 54 |
| /community/awards/psf-awards/ | Still live | 301 -> 200 | /community/awards/psf-awards/ | No -- live: /community/awards/psf-awards/; plan: /psf/sponsorship/ | 29 |
| /community/jobs/howto/ | Still live | 301 -> 200 | /community/jobs/howto/ | No -- live: /community/jobs/howto/; plan: /jobs/type/lead/ | 25 |
| /about/success/acqutek/ | Still live | 301 -> 200 | /about/success/acqutek/ | No -- live: /about/success/acqutek/; plan: /success-stories/category/arts/ | 21 |
| /about/success/esr/ | Still live | 301 -> 200 | /about/success/esr/ | No -- live: /about/success/esr/; plan: /success-stories/category/business/ | 21 |
| /about/success/guards/ | Still live | 301 -> 200 | /about/success/guards/ | No -- live: /about/success/guards/; plan: /success-stories/category/education/ | 21 |
| /about/success/strakt/ | Still live | 301 -> 200 | /about/success/strakt/ | No -- live: /about/success/strakt/; plan: /success-stories/category/software-development/ | 21 |
| /community/pycon/ | Still live | 301 -> 200 | /community/pycon/ | No -- live: /community/pycon/; plan: /psf/volunteer/pycon/ | 16 |
| /community/sigs/current/distutils-sig/doc/ | Still live | 301 -> 200 | /community/sigs/current/distutils-sig/doc/ | No -- live: /community/sigs/current/distutils-sig/doc/; plan: /doc/ | 16 |
| /community/jobs/index.html | To parent section | 301 -> 301 -> 200 | /community/jobs/ | No -- live: /community/jobs/; plan: /jobs/type/back-end/ | 15 |
| /community/index.html | Not found (404) | 301 -> 404 | /community/index.html | -- | 10 |
| / | Still live | 301 -> 200 | / | -- | 65 |
| /about/ | Still live | 301 -> 200 | /about/ | -- | 65 |
| /about/legal/ | Still live | 301 -> 200 | /about/legal/ | -- | 60 |
| /community/ | Still live | 301 -> 200 | /community/ | -- | 55 |
| /about/help/ | Still live | 301 -> 200 | /about/help/ | -- | 54 |
| /about/apps/ | Still live | 301 -> 200 | /about/apps/ | -- | 54 |
| /about/gettingstarted/ | Still live | 301 -> 200 | /about/gettingstarted/ | -- | 54 |
| /about/quotes/ | Still live | 301 -> 200 | /about/quotes/ | -- | 54 |
| /community/lists/ | Still live | 301 -> 200 | /community/lists/ | -- | 54 |
| /community/logos/ | Still live | 301 -> 200 | /community/logos/ | -- | 54 |
| /community/sigs/ | Still live | 301 -> 200 | /community/sigs/ | -- | 54 |
Cross-page analysis confirms these site-wide SEO strengths.
Cross-page analysis identified these site-wide patterns worth reviewing.
| Finding | Recommendation |
|---|---|
|
Recommended
SITE: 2 pages share duplicate title "Welcome to Python.org"
▶
2 affected pages
|
Site-wide observation: 2 pages share duplicate title "Welcome to Python.org". |
|
Recommended
SITE: 11 pages share duplicate title "Python Job Board | Python.org"
▶
11 affected pages
|
Site-wide observation: 11 pages share duplicate title "Python Job Board | Python.org". |
|
Recommended
SITE: 5 pages share duplicate title "Our Events | Python.org"
▶
5 affected pages
|
Site-wide observation: 5 pages share duplicate title "Our Events | Python.org". |
|
Recommended
SITE: 95 pages share duplicate meta description
▶
95 affected pages
|
Site-wide observation: 95 pages share duplicate meta description. |
|
Recommended
SITE: 34 internal links use HTTP instead of HTTPS
▶
4 affected pages
|
Site-wide observation: 34 internal links use HTTP instead of HTTPS. |
| Finding | Recommendation |
|---|---|
| MISSING: H1 tag | Adding a clear H1 heading would help both visitors and search engines understand this page's main topic at a glance. |
| Finding | Recommendation |
|---|---|
| MISSING: H1 tag | Adding a clear H1 heading would help both visitors and search engines understand this page's main topic at a glance. |
| Finding | Recommendation |
|---|---|
| MISSING: H1 tag | Adding a clear H1 heading would help both visitors and search engines understand this page's main topic at a glance. |
| Finding | Recommendation |
|---|---|
| MISSING: H1 tag | Adding a clear H1 heading would help both visitors and search engines understand this page's main topic at a glance. |
| Finding | Recommendation |
|---|---|
| MISSING: H1 tag | Adding a clear H1 heading would help both visitors and search engines understand this page's main topic at a glance. |
| Finding | Recommendation |
|---|---|
| MISSING: H1 tag | Adding a clear H1 heading would help both visitors and search engines understand this page's main topic at a glance. |
| Finding | Recommendation |
|---|---|
| MISSING: H1 tag | Adding a clear H1 heading would help both visitors and search engines understand this page's main topic at a glance. |
| Finding | Recommendation |
|---|---|
| MISSING: H1 tag | Adding a clear H1 heading would help both visitors and search engines understand this page's main topic at a glance. |
| Finding | Recommendation |
|---|---|
| META: Description too long (259 chars, recommended max 160) | The meta description is 259 characters. Search engines typically show up to 160 characters. A shorter description ensures the full snippet is visible. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 2 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (2 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| META: Title too long (96 chars, recommended max 60) | The title tag is 96 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 2 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (2 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| META: Title too long (64 chars, recommended max 60) | The title tag is 64 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 3 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (3 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| META: Title too long (72 chars, recommended max 60) | The title tag is 72 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| META: Title too long (61 chars, recommended max 60) | The title tag is 61 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 12 of 13 images missing alt text | Some images are missing alt text (12 of 13 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 175 of 176 images missing alt text | Some images are missing alt text (175 of 176 images missing alt text). Adding descriptive alt attributes improves accessibility for screen readers and helps search engines understand image content. |
| ACCESSIBILITY: 176 images missing width/height (layout shift risk) | Some images lack explicit dimensions (176 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. |
| ACCESSIBILITY: 55 form inputs missing labels | Some form inputs lack associated labels (55 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 35 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (35 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 16 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (16 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 15 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (15 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 8 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (8 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 4 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (4 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 38 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (38 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 15 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (15 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 10 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (10 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 6 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (6 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 9 images missing width/height (layout shift risk) | Some images lack explicit dimensions (9 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. |
| LINKS: 7 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (7 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 7 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (7 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| META: Title too long (65 chars, recommended max 60) | The title tag is 65 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 4 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (4 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 2 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (2 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| ACCESSIBILITY: 1 iframes without title attribute | Some iframes lack title attributes (1 iframes without title attribute). Adding titles improves accessibility by helping screen readers describe embedded content. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| META: Title too long (65 chars, recommended max 60) | The title tag is 65 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| META: Title too long (74 chars, recommended max 60) | The title tag is 74 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 12 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (12 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 5 images missing width/height (layout shift risk) | Some images lack explicit dimensions (5 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 6 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (6 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 2 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (2 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 10 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (10 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 10 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (10 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 18 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (18 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| ACCESSIBILITY: 1 iframes without title attribute | Some iframes lack title attributes (1 iframes without title attribute). Adding titles improves accessibility by helping screen readers describe embedded content. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| LINKS: 1 mixed-content links (HTTP on HTTPS page) | Some links on this HTTPS page point to HTTP URLs (1 mixed-content links (HTTP on HTTPS page)). Updating these to HTTPS ensures a consistent secure experience and avoids mixed-content browser warnings. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| ACCESSIBILITY: 5 images missing width/height (layout shift risk) | Some images lack explicit dimensions (5 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| ACCESSIBILITY: 1 form inputs missing labels | Some form inputs lack associated labels (1 form inputs missing labels). Adding labels improves accessibility and usability for all visitors, especially those using assistive technology. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| META: Title too long (64 chars, recommended max 60) | The title tag is 64 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| 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. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| ACCESSIBILITY: 1 iframes without title attribute | Some iframes lack title attributes (1 iframes without title attribute). Adding titles improves accessibility by helping screen readers describe embedded content. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| META: Title too long (97 chars, recommended max 60) | The title tag is 97 characters. Search engines typically display up to 60 characters. Trimming the title would ensure it appears fully in results. |
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| ACCESSIBILITY: 19 images missing width/height (layout shift risk) | Some images lack explicit dimensions (19 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| MISSING: Canonical tag | A canonical tag would help search engines identify the preferred version of this page, especially if it's accessible through multiple URLs. |
| SCHEMA: WebSite missing required property: name | The structured data is WebSite missing required property: name. Adding the missing property would help search engines fully understand this content and may enable richer search results. |
| 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. |
| LINKS: 5 JavaScript-only links (not crawlable) | Some links use JavaScript instead of standard URLs (5 JavaScript-only links (not crawlable)). Search engine crawlers cannot follow JavaScript links, which may prevent those destination pages from being discovered and indexed. |
| Finding | Recommendation |
|---|---|
| REDIRECT: 301 redirect to https://www.python.org/psf-landing/ | Note: REDIRECT: 301 redirect to https://www.python.org/psf-landing/ |
| Finding | Recommendation |
|---|---|
| REDIRECT: 302 redirect to an off-site URL (https://policies.python.org/python.org/code-of-conduct/) -- not crawled | Note: REDIRECT: 302 redirect to an off-site URL (https://policies.python.org/python.org/code-of-conduct/) -- not crawled |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 6 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 (9.6%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.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 (216 KB, recommended <100KB) | The page weighs 216 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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. |
| SOCIAL: OG tags incomplete (3/4 present) | Open Graph tags are partially configured (OG tags incomplete (3/4 present)). Completing all four OG tags (title, description, image, url) ensures attractive previews when the page is shared on Facebook, LinkedIn, and other social platforms. |
| CONTENT: Very low text-to-HTML ratio (7.8%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.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 (236 KB, recommended <100KB) | The page weighs 236 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 5 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 (8.5%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 5 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 10 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (9.9%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 3 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 11 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 5 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 10 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. |
| STRUCTURE: Deprecated HTML elements found: <tt> | This page uses deprecated HTML elements (Deprecated HTML elements found: <tt>). Replacing these with modern CSS-styled equivalents improves code quality and ensures consistent rendering across browsers. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (8.2%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (8.0%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.0%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (8.3%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (8.5%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (7.8%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (8.7%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (8.7%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (7.8%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| SOCIAL: OG tags incomplete (3/4 present) | Open Graph tags are partially configured (OG tags incomplete (3/4 present)). Completing all four OG tags (title, description, image, url) ensures attractive previews when the page is shared on Facebook, LinkedIn, and other social platforms. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 6 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 (8.9%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 6 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 (9.8%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.8%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| SECURITY: 1 links with target="_blank" missing rel="noopener" | Some links open in new tabs without rel="noopener" (1 links with target="_blank" missing rel="noopener"). Adding 'noopener' prevents the opened page from accessing the originating window, which is a security best practice. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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 (7.5%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 9 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 (6.1%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.1%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 4 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 (9.9%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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 (9.9%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 7 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 6 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 13 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (8.9%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 3 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (19 chars, recommended min 70) | The meta description is only 19 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 5 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 5 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 4 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 4 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (9.3%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 3 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (8.2%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.2%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: Large page (349 KB, recommended <100KB) | The page weighs 349 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: Large page (583 KB, recommended <100KB) | The page weighs 583 KB. Reducing page size (target <100KB for HTML) through minification, removing unused code, or optimizing embedded content would improve load times. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 4 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (9.7%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.7%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 12 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 11 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 3 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| SECURITY: 1 links with target="_blank" missing rel="noopener" | Some links open in new tabs without rel="noopener" (1 links with target="_blank" missing rel="noopener"). Adding 'noopener' prevents the opened page from accessing the originating window, which is a security best practice. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 7 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 4 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 13 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 7 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 8 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 3 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 7 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 13 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| MULTIPLE H1: 3 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| 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. |
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (6.9%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (6.9%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (8.6%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (8.6%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (7.5%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (7.5%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| CONTENT: Very low text-to-HTML ratio (9.3%) | This page has a low text-to-HTML ratio (Very low text-to-HTML ratio (9.3%)). This may indicate heavy template markup or limited unique content. Increasing meaningful text content would strengthen the page's search relevance. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| 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: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| MULTIPLE H1: 4 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. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| META: Description too short (52 chars, recommended min 70) | The meta description is only 52 characters. A more detailed description (70-160 chars) would give users a better preview in search results. |
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
| Finding | Recommendation |
|---|---|
| PERFORMANCE: 1 render-blocking scripts in <head> | There are 1 render-blocking script(s) in the <head>. Adding 'async' or 'defer' attributes to these scripts would allow the page to begin rendering sooner, improving perceived load time. |
These elements have been properly implemented, demonstrating strong SEO foundations. Click any page to expand its findings.
Recommended 301 permanent redirects from python.org (Wayback Machine, December 2013) to python.org (live today). 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 |
|---|---|---|---|---|---|---|
| /about/help | /about/help | Exact | 100% | Still live | -- | |
| /community | /community | Exact | 100% | Still live | -- | |
| / | / | Exact | 100% | Still live | -- | |
| /about | /about | Exact | 100% | Still live | -- | |
| /about/apps | /about/apps | Exact | 100% | Still live | -- | |
| /about/gettingstarted | /about/gettingstarted | Exact | 100% | Still live | -- | |
| /about/legal | /about/legal | Exact | 100% | Still live | -- | |
| /about/quotes | /about/quotes | Exact | 100% | Still live | -- | |
| /community/awards | /community/awards | Exact | 100% | -- | -- | |
| /community/diversity | /community/diversity | Exact | 100% | -- | -- | |
| /community/irc | /community/irc | Exact | 100% | -- | -- | |
| /community/jobs/index.html | /jobs/type/back-end | title | 100% | Title similarity: 100% | To parent section | No -- live: /community/jobs/; plan: /jobs/type/back-end/ |
| /community/lists | /community/lists | Exact | 100% | Still live | -- | |
| /community/logos | /community/logos | Exact | 100% | Still live | -- | |
| /community/sigs | /community/sigs | Exact | 100% | Still live | -- | |
| /community/jobs | /jobs | Slug | 85% | Matched on slug: 'jobs' | Still live | No -- live: /community/jobs/; plan: /jobs/ |
| /community/pycon | /psf/volunteer/pycon | Slug | 85% | Matched on slug: 'pycon' | Still live | No -- live: /community/pycon/; plan: /psf/volunteer/pycon/ |
| /community/sigs/current/distutils-sig/doc | /doc | Slug | 85% | Matched on slug: 'doc' | Still live | No -- live: /community/sigs/current/distutils-sig/doc/; plan: /doc/ |
| /about/success | /success-stories | title | 82% | Title similarity: 83% | Still live | No -- live: /about/success/; plan: /success-stories/ |
| /about/success/acqutek | /success-stories/category/arts | title | 78% | Title similarity: 78% | Still live | No -- live: /about/success/acqutek/; plan: /success-stories/category/arts/ |
| /community/index.html | /dev/security | title | 77% | Title similarity: 77% | Not found (404) | -- |
| /about/success/strakt | /success-stories/category/software-development | Keyword | 42% | Keyword overlap: 43% | Still live | No -- live: /about/success/strakt/; plan: /success-stories/category/software-development/ |
| /community/jobs/howto | /jobs/type/lead | Keyword | 42% | Keyword overlap: 43% | Still live | No -- live: /community/jobs/howto/; plan: /jobs/type/lead/ |
| /about/success/esr | /success-stories/category/business | Keyword | 40% | Keyword overlap: 40% | Still live | No -- live: /about/success/esr/; plan: /success-stories/category/business/ |
| /about/success/guards | /success-stories/category/education | Keyword | 40% | Keyword overlap: 40% | Still live | No -- live: /about/success/guards/; plan: /success-stories/category/education/ |
| /community/awards/psf-awards | /psf/sponsorship | Keyword | 40% | Keyword overlap: 40% | Still live | No -- live: /community/awards/psf-awards/; plan: /psf/sponsorship/ |
| /about/success/astra | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/carmanah | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/honeywell | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/ilm | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/rackspace | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/merchandise | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /3kpoll | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /about/success/bats | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/cog | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/devil | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/devnet | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/dlink | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/enovad | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/ezro | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/forecastwatch | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/frequentis | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/gravityzoo | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/gusto | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/journyx | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/loveintros | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/mayavi | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/mmtk | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/natsworld | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/nexedi | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/philips | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/projectpipe | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/resolver | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/siena | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/st-andrews | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/superleague | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /about/success/suzanne | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/tempest | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/testgo | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/tribon | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/tttech | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/usa | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/verity | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/wingide | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/wordstream | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/success/xist | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /about/website | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /cgi-bin/psf/payment.py | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /community/awards/frank-willison | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/awards/frank-willison/2006-martelli | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/awards/psf-distinguished-awards | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/coordination | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/capi-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/catalog-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /community/sigs/current/catalog-sig/others | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /community/sigs/current/catalog-sig/requirements | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /community/sigs/current/cplusplus-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/db-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/db-sig/status | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/distutils-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/distutils-sig/doc/requirements | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/distutils-sig/sig_charter | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /community/sigs/current/doc-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/doc-sig/otherlangs | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/doc-sig/stext | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/edu-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/edu-sig/old_page | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /community/sigs/current/email-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/i18n-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/image-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/image-sig/status | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/image-sig/t1lib | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/import-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/meta-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/pythonmac-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/stdlib-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/uls-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Not found (404) | -- |
| /community/sigs/current/web-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| /community/sigs/current/xml-sig | (needs redirect target) | unmatched | 0% | No equivalent page found on the new site | Still live | -- |
| DOC /community/clpya-guidelines.txt | (needs redirect target) | unmatched_document | 0% | Document not found on new site | Still live | -- |
| DOC /community/jobs/howto/job-template.txt | (needs redirect target) | unmatched_document | 0% | Document not found on new site | Not found (404) | -- |
| DOC /files/miller-dissertation.pdf | (needs redirect target) | unmatched_document | 0% | Document not found on new site | Not found (404) | -- |