This report combines Core Trac, Gutenberg GitHub issues, wordpress-develop PRs, WordPress.org ecosystem data, WordCamp records, Make/Core posts, W3Techs market-share trends, and HTTP Archive context. Ticket data explains project load. Market data explains whether people still choose WordPress.
Core Trac, Gutenberg GitHub issues, and wordpress-develop PRs explain project participation and maintenance load. See the project load view for the compact workload readout.
WordPress.org APIs, Make/Core, WordCamp, Events, Translate, Five for the Future, and support snapshots show community activity outside trackers. See the ecosystem activity view for the compact digest and the support load view for the current support-queue readout.
W3Techs, HTTP Archive, BuiltWith, Stack Overflow, Wikimedia, Hacker News, jobs, and plugin history show market position and demand proxies. See the market position view for the compact decision readout, the new-site choice view for current pipeline and crawl proxies, the search interest view for public-attention proxies, the developer interest view for help-seeking and PR activity, and the job demand view for hiring proxies.
WordPress remains the default CMS on installed-share and ecosystem evidence. The softer parts are new-site momentum, first-time tracker participation, and demand signals that currently rely on public proxies.
All-site share and CMS share still make WordPress the default CMS.
All-site W3Techs change since Jan 2025; CMS share also moved -2.7 pts.
Share of the tracked 90-day BuiltWith pipeline across WordPress, Shopify, Wix, and Webflow.
Core and Gutenberg first-time reporter retention versus the 2021-2023 quarterly average.
Core and Gutenberg closure/new ratios since 2024.
Current WordPress.org plugin and theme directory counts, plus active releases, events, translations, and pledges elsewhere in the report.
Read this from strongest to most provisional: installed share is direct, current newly found-site counts are a useful proxy, recurring crawl trend shows direction, and a true first-seen cohort source is still the next source to add.
Direct W3Techs all-site and CMS-share context.
BuiltWith 90-day tracked newly found-site share; 30-day share is 60.4%.
HTTP Archive tracked-share movement since 2020-01-01.
Needs first-seen site cohort or paid BuiltWith historical export.
These signals help separate public attention, developer help-seeking, and hiring demand. They are useful directional evidence, but they are not a substitute for search-provider or broad hiring-platform exports.
Wikimedia WordPress pageviews versus the latest pre-2024 quarter.
Stack Overflow WordPress-tag questions versus the latest pre-2024 quarter.
HN WP/Woo hiring mention rate versus parsed pre-2024 history.
Needs Google Trends or similar plus a broad hiring-platform export.
Support data is strongest for the current queue shape and major-plugin support load. It is weaker for long-term trend claims until a full support-forum history or recurring snapshots are added.
25.9% resolved, 73.2% unresolved in the sampled support queue.
Unresolved topics with last activity 91+ days ago.
77.7% resolved across tracked major-plugin support threads.
Needs a full topic/reply export or recurring all/resolved/unresolved snapshots.
WordPress still has the largest installed CMS footprint and a broad plugin, theme, and community surface.
41.5% of all sites; 59.3% of CMS sites.First-time tracker participation and public help-question volume are lower than earlier periods.
First-time reporter retention: Core 66.2%, Gutenberg 69.5%.The report has useful public proxies, but the ideal sources are first-seen site cohorts, search-provider exports, and broad hiring-platform exports.
Current BuiltWith 90-day proxy: 67.4% WordPress share.W3Techs has WordPress at 41.5% of all sites and 59.3% of CMS sites, down 2.1 and 2.7 points since Jan 2025.
Core first-time reporters averaged 226.4 per quarter in 2021-2023 and 149.8 since 2024. Gutenberg moved from 114.5 to 79.6.
Since 2024, Core closures slightly exceed new tickets on average. Gutenberg is close to flat, with the latest sampled quarter closing 582 against 426 new issues.
wordpress-develop PR creation averaged 413.8 per quarter in 2021-2023 and 632.5 since 2024. Line review comments averaged 1,666 per quarter since 2024.
This map separates direct measurements from mixed or proxy-backed answers. Use it to decide which conclusions are already well supported and which ones need one more source before an important new-site or demand decision.
Yes.
W3Techs installed share, HTTP Archive, traffic-tier snapshots
No extra source needed for installed-share direction.
Softer recently.
W3Techs yearly trend plus HTTP Archive recurring crawl share
A true first-seen site cohort would make new-site momentum clearer.
Fewer new tracker reporters.
Core Trac, Gutenberg GitHub issues, wordpress-develop PRs
Outside-ticket channels are shown separately in ecosystem activity.
Mostly.
Quarterly Core and Gutenberg new/closed flow
Keep watching closure waves against new issue/ticket volume.
Aged.
Current open Core and Gutenberg backlog age buckets
Current support history still needs a longer forum export.
Broad entry, concentrated work.
Top 10/25/50 contributor shares across tickets, issues, and PRs
Pair with contributor-depth cohorts before reading concentration alone.
Some share, yes.
BuiltWith current pipeline and HTTP Archive tracked share
Needs a first-seen site cohort or paid BuiltWith historical export.
Visible, but slower.
Wikimedia, Stack Overflow, HN hiring, WordPress Jobs board
Needs search-provider and broad hiring-platform exports.
These are the plain-English answers the report is meant to support. Each card points to the kind of evidence behind the answer, so this can be used as a quick briefing before reading the charts.
Installed-share evidence has WordPress at 41.5% of all sites and 59.3% of CMS sites.
W3Techs + HTTP ArchiveW3Techs is down 2.1 all-site points and 2.7 CMS-share points since Jan 2025.
W3Techs yearly trendCore first-time reporter retention is 66.2% of the 2021-2023 average; Gutenberg is 69.5%. PR and review-comment activity remain visible.
Core Trac + Gutenberg + PRsSince 2024, closure/new ratios are Core 103.5% and Gutenberg 98.3%.
Quarterly ticket flowOpen stale share is Core 75.0% and Gutenberg 64.4%; 2+ year open share is Core 59.7% and Gutenberg 39.9%.
Current open backlogSince 2024, top-50 work share is Core 35.9%, Gutenberg 50.8%, and PRs 65.0%.
Contributor concentrationHTTP Archive tracked share has WordPress at 78.9%, -10.8 pts since 2020-01-01; WordPress still leads the current tracked BuiltWith 90-day pipeline at 67.4%.
HTTP Archive + BuiltWith proxyThe main participation change is not a collapse. It is fewer first-time and unique reporters in the trackers, while PR authorship is steadier and code review still has visible quarterly traffic. The companion contributor depth view breaks this down into drive-by, returning, regular, and sustained participation.
This separates new-arrival volume from follow-on participation. It asks: of the people first seen in a quarter, how many came back within the next year?
Rows are stored in SQLite as contributor_retention_cohorts. The newest cohorts are intentionally excluded from this chart until they have enough follow-up time.
This is the closest available maintainer/non-maintainer split for GitHub-originated activity. It is based on the author's relationship to the repository at collection time, not on who reviewed or merged the work.
Share of work since 2024 handled by the top 10, 25, and 50 people in each source.
Share of contributors since 2024 who opened exactly one ticket, issue, or PR.
Share of work since 2024 coming from people with 20 or more tickets, issues, or PRs in that same window.
Comments show who is participating in Make/Core discussion, which is separate from who publishes posts.
Attendance is not populated on every record. This uses the API's anticipated-attendee field when present.
Current translate.wordpress.org locale directory. Contributor counts are locale-team profile counts, not globally deduplicated people.
Current WordPress Core development project translation status by locale.
Top locale teams by listed profile count in the current Translate WordPress directory.
Translation activity is broad and ongoing. The current snapshot shows many locale teams, but Core development coverage is uneven because every active development branch creates new strings.
Current events.wordpress.org map payload. This captures scheduled upcoming activity, not historical attendance.
Groups with the most scheduled upcoming events in the current Events listing.
Meetups dominate the upcoming event calendar; WordCamps remain visible as larger scheduled events.
Current public WordPress.org support views plus a compact quarterly archive estimate for historical context.
Deduplicated topics across the current public queue views, grouped by forum and sorted by unresolved topics.
How old the unresolved queue is, measured from each topic's last activity date at collection time.
Credits are a broader community signal than commit access. They include people credited in release props, including non-committers.
This uses exact GitHub compare ranges between release tags, so it is narrower than credits and closer to commit access/activity.
Current pledge listing from WordPress.org. This is a present-day ecosystem signal, not a historical trend.
Top listed organizations by pledged hours per week.
The workload picture is healthier than the reporter trend alone suggests: Core has been near or below net-zero since 2024, and Gutenberg had a clear cleanup quarter in 2026-Q2. The backlog is still large.
Latest closure quarter: median is the typical closed ticket or issue; p90 shows older work that was still being closed.
Median of quarterly median days-to-close since 2024, which smooths out single cleanup pulses.
Core uses Trac RSS entries for tickets created since 2021. Gutenberg uses GitHub GraphQL comments and reopen timelines for the existing issue inventory.
These are direct tracker-derived signals, not adoption signals.
Currently open Trac tickets grouped by time since last modification.
Currently open GitHub issues grouped by time since last update.
Open classified Trac tickets by category. Bars show open counts; percentages are category share of the open Core backlog.
Open classified GitHub issues by category. Bars show open counts; percentages are category share of the open Gutenberg backlog.
The market signal is: WordPress is still far ahead, but its share has flattened and recently declined while hosted builders gained small, distributed share. Read this section as three evidence layers: measured installed share, current newly found-site proxy, and demand/attention proxies.
These signals answer different questions. Installed-share sources are the strongest adoption evidence. BuiltWith's 90-day pipeline is useful for current direction, but it is not a multi-year new-site cohort. Developer, hiring, and public-interest sources are demand proxies.
If the question is whether WordPress is still widely chosen, use W3Techs, HTTP Archive, and traffic-tier presence. If the question is whether new builders are choosing it right now, use BuiltWith cautiously and compare it with hosted-builder momentum. If the question is developer mindshare, use the demand proxies below.
Current autocomplete suggestions for selected WordPress, developer, alternatives, and comparison queries. This shows query themes, not search volume.
Seed queries are stored in SQLite as search_query_suggestions with rank, locale, source URL, and intent bucket.
HTTP Archive adds a monthly crawl-based adoption view. It is useful for direction and comparison, but it counts detected origins in the crawl rather than new site creation.
This is not a new-site cohort, but it is a recurring crawl-based comparison of WordPress against hosted builders and ecommerce platforms in the same detected-origin dataset.
Core Web Vitals adds a field-quality view next to adoption. This measures the share of crawled origins with good mobile user-experience signals, not project ticket volume.
Latest mobile-crawl origin counts by HTTP Archive rank tier. The percentages are WordPress share among the five tracked technologies, not share of the entire tier.
Peer comparison within the tracked set: WordPress, Shopify, Wix, Squarespace, and Webflow. This shows whether WordPress remains ahead in higher-traffic tiers.
Current WordPress.org stats API distribution. This is an installed-base snapshot from update checks, not a history of new sites.
Current PHP and database distribution from WordPress.org stats. This adds deployment-context evidence for performance and compatibility decisions.
Compact direction check across the report's public attention, developer-help, hiring, and WordPress-specific job-board proxies. These rows are directional; they do not replace Google Trends or a broad labor-market export.
Rows are stored in SQLite as attention_demand_summary. Baselines use the latest available pre-2024 quarter or archived snapshot where the source supports it.
Stack Overflow tag volume is much narrower than overall site-builder demand, but it shows whether developers are asking for help with WordPress and comparable builder/ecommerce ecosystems.
Full 2010-Q1 to 2026-Q2 coverage: WordPress, WooCommerce, Shopify. Partial coverage: Wix 61/66, Squarespace 22/66, Webflow 22/66.
Wikimedia article views help separate broad public attention from developer-help and hiring signals. They are a proxy, not a direct measure of site-builder selection.
This is a narrow startup-hiring proxy from HN threads, not a complete job-market view. Direct WordPress/WooCommerce mentions are small; PHP and agency/studio mentions give useful adjacent context.
Summary rows are stored in SQLite as hn_hiring_demand_summary, remoteok_job_signal_snapshot, and remotive_job_signal_snapshot.
Open listings on jobs.wordpress.net add a WordPress-specific demand signal. The series is a snapshot view: it counts visible open listings on captured pages, not total postings over the whole year.
Current public WordPress VIP case-study records. This is a curated enterprise evidence source, not a count of all enterprise WordPress sites.
Latest public case-study posts from WordPress VIP. Use-case terms are sparse in the API, so industry mix is the better structured view.
Compact current-direction summary from BuiltWith newly found-site counts, HTTP Archive tracked-share history, and BuiltWith traffic-tier presence. See the new-site choice view for the easier visual readout.
Rows are stored in SQLite as new_site_choice_summary. Use this as a decision summary, then inspect the BuiltWith and HTTP Archive charts below for source context.
The public sources do not expose a historical first-published-site CMS cohort. The closest public quarter-level proxy here is HTTP Archive detected-origin movement: how the recurring crawl's detected origins changed from one quarter to the next.
Rows are stored in SQLite as http_archive_quarterly_detected_origin_change. A 0% addition share means WordPress had no positive net detected-origin growth that quarter while at least one tracked peer did. Sources checked: BuiltWith Net New Pipeline, HTTP Archive Technology Report API, HTTP Archive BigQuery guide, and W3Techs methodology.
The five-way chart above is intentionally narrow: WordPress, Shopify, Wix, Squarespace, and Webflow. The chart below puts the broader selected signals into one all-sites split: WordPress, Shopify, other CMS/builders, Next.js, static/app generators, AI/visual builders, and everything else. The residual includes custom apps, pure/static HTML, unknown/no detected site-creation tool, deployment surfaces, and tools outside this selected set.
Latest selected-bucket split from the all-sites line chart. All other sites/tools includes pure HTML, custom apps, unknown/no detected tool, deployment-only signals, and tools outside the selected buckets.
Rows are stored in SQLite as http_archive_site_creation_adoption_monthly.
Latest quarterly split of positive net detected-origin additions. Buckets with net losses in the quarter contribute 0% to this readout.
Latest bucket: 2026-Q2. Use this as a directional new-site proxy until an origin-level first-seen export is available.
BuiltWith public Net New Pipeline counts for the last 90 days. Squarespace's top-level CMS page does not expose new-site counts, so it is excluded from this share.
BuiltWith traffic-tier counts show where each technology appears among higher-traffic sites.
BuiltWith current counts across WordPress, Shopify, Wix, Squarespace, and Webflow. Long tail means live sites outside the Top 1M tier.
WooCommerce appears in both BuiltWith ecommerce tracking and the WordPress.org plugin directory.
Current live-site totals from the fetched BuiltWith ecommerce pages.
Current WordPress.org plugin directory browse samples. The 90-day counts show a prefix when the API sample hit the page cap before passing 90 days.
Current WordPress.org plugin search-result counts for selected site-builder, commerce, operations, and emerging categories. Broad terms can hit the API result cap.
Popular plugin pages from the WordPress.org API. Stale here means last updated more than two years before the snapshot date.
Fixed-slug WordPress.org plugin API snapshot for widely used plugins. Active installs are rounded and overlap across sites, so they show ecosystem reach, not unique adoption.
Two years of WordPress.org daily download stats for the same fixed major-plugin list. Downloads show update and demand activity; they are not active installs.
Current WordPress.org plugin API support-thread counts for the fixed major-plugin list. This is a snapshot of visible support load, not a long-term forum trend.
Resolved share for the highest-load tracked plugins. Unresolved counts highlight where current visible support queues are heavier.
These archived plugin-page values are rounded active-install buckets, but they add direction to the current snapshot and help separate mature install reach from short-term download activity.
The theme API exposes browse lists but not add/update dates in the sampled rows, so this is a current directory shape snapshot rather than a trend.
Current WordPress.org theme search-result counts for selected site categories. This is a current breadth snapshot, not a theme-install trend.
Top sampled popular themes ranked by rating count in the current WordPress.org theme API response.
This is the quick read on how much weight to put on each part of the report. The strongest areas have direct quarterly data. Softer areas use snapshots or public proxies because a full historical market export is not available here.
Core Trac, Gutenberg issues, and wordpress-develop PRs.
Use for new vs closed work, net flow, open backlog, response time, close time, stale share, and reopened rate.
Reporters, first-time people, repeat people, PR authors, and contributor depth.
Use for whether participation is broadening or narrowing. The current answer is fewer new tracker reporters, while PR flow is steadier.
Classified Core and Gutenberg tickets/issues.
Use the separate bug, feature-request, enhancement, task, and all-ticket views instead of a stacked total.
Props, committers, Make/Core, WordCamps, translations, Five for the Future, plugins, and themes.
Good for showing activity outside ticket trackers. Some series are historical; others are current snapshots.
W3Techs, HTTP Archive, BuiltWith traffic tiers, WordPress.org stats.
Use for whether WordPress is still widely used. It is still the default CMS, but recent share signals are softer.
BuiltWith 30/90-day pipeline plus recurring HTTP Archive origin counts.
Use for current direction only. It is not a multi-year newly created site cohort.
Stack Overflow, Wikimedia, HN hiring, and WordPress Jobs snapshots.
Useful for public/developer attention, but not a replacement for Google Trends or a broad hiring-platform export.
Current WordPress.org support queues, archive estimates, and major-plugin support counts.
Use for current queue shape and rough historical support-view direction. A full forum export would make topic-level trend claims stronger.
The SQLite database stores imported source tables, fetched ecosystem/adoption records, file hashes, and explicit source gaps. Download: community_health.sqlite.gz. Inventory: data_inventory.html. Source gap plan: source_gap_plan.html. Goal audit: goal_audit.html.
The report is built from local ticket exports plus public-source fetches. The SQLite database stores source-file paths, row counts, and SHA-256 hashes for local imports, so a later refresh can verify whether the underlying exports changed. The data inventory lists the current tables, source hashes, and partial-source gaps.
Run the report generator to refresh public sources, or use cached data when validating layout and wording. After any database change, regenerate the data inventory too. The supporting fetch scripts keep Core response metrics, Gutenberg timelines, and support snapshots reproducible.
python3 make_community_health_report.py
python3 make_community_health_report.py --skip-network
python3 refresh_report_artifacts.py
python3 make_goal_audit.py
python3 make_data_inventory.py
fetch_core_response_metrics.py
fetch_gutenberg_timeline_metrics.py
fetch_support_forum_snapshot.py
Use these alongside the main report depending on whether the reader needs a short decision brief, current progress, source audit, or refresh instructions.
These are the main places where the report uses a proxy or snapshot instead of a full historical source.
Short version: WordPress is still widely chosen on installed-share evidence; current new-site and demand proxies are softer; ticket participation has fewer new reporters; project load is closer to balanced than the backlog size alone suggests.
W3Techs, Core Trac, Gutenberg issues, PRs, releases, and WordPress.org APIs support the strongest claims.
HTTP Archive monthly origin counts show WordPress at 78.9% of the tracked set, -10.8 pts since 2020-01-01.
BuiltWith pipeline, Wikimedia, Stack Overflow, HN hiring, and Jobs snapshots point to direction but are not complete market measures.
Google Trends or similar, labor-market exports, and a fuller support-forum history would make those signals stronger.
Core and Gutenberg still get steady participation, but fewer first-time reporters are entering the trackers than in 2021-2023. PR and review-comment activity are still visible.
Release credits, committers, WordCamps, translations, pledged work, and support queues show community surface area beyond tickets. These are mostly release-level or current snapshots, so they describe depth more than quarter-to-quarter momentum.
WordPress 7.0
7.0
2025 full-year records
202 locale teams
Five for the Future weekly
25.9% resolved share
Since 2024, Core closures are slightly above new tickets on average, and Gutenberg is near balanced with a recent cleanup quarter. The remaining open backlog still contains a large older share.
W3Techs has WordPress at 41.5% of all sites and 59.3% of CMS sites, down 2.1 and 2.7 points since Jan 2025. BuiltWith's current 90-day pipeline still shows WordPress with the largest tracked new-site count among WordPress, Shopify, Wix, and Webflow, but that is a current proxy rather than a historical new-site trend.