WordPress report source gap plan

A visual collection plan for the partial-source areas already stored in source_gaps. This page does not change the current report status; it makes the next data pulls explicit and refreshable.

Partial signals

5Stored in source_gaps.

Database tables

110Existing report tables remain intact.

Integrity

okSQLite integrity check.

Next mode

1 at a timeImport, validate, then publish each source family.

Collection order

Start with new-site history because it most directly answers whether people still choose WordPress for new builds. Search interest and job demand are next because they broaden the demand picture beyond tickets.

1
New-site choice history

Quarterly WordPress, Shopify, Wix, Squarespace, and Webflow rows across multiple years.

2
Search interest

Normalized quarterly search series for WordPress and peer builders, plus refreshable query-intent snapshots.

3
Job demand

Quarterly WordPress, PHP, CMS, Shopify, Wix, Squarespace, and Webflow demand rows, with the current WordPress Jobs board proxy already stored quarterly.

4
Support history

Quarterly topics opened, resolved, unresolved, unanswered, reply counts, and response-age rows from a topic-level source.

5
Developer interest

Developer-attention rows that combine help questions, public attention, package use, Composer ecosystem usage, and contribution activity.

1

New-site choice history

Separates installed presence from whether new site builders are choosing WordPress now.

Current coverage

Current report includes BuiltWith current Net New Pipeline, HTTP Archive monthly origin counts, quarterly derived tracked-share history, quarter-over-quarter detected-origin change proxies, broader site-creation mode signals, builder momentum summaries, rank-tier detected-origin adoption, a compact new-site choice summary, and a dedicated new-site choice companion view; not a multi-year first-published-site cohort.

Best next source

BuiltWith historical trends or HTTP Archive cohort queries

Collection step

Add a paid BuiltWith historical trend export or an HTTP Archive first-seen-origin cohort query.

Target tables

new_site_cohort_quarterly builder_new_site_share_quarterly

Done when Quarterly WordPress, Shopify, Wix, Squarespace, and Webflow rows across multiple years.
2

Search interest

Turns the current Wikimedia, Stack Overflow, and autocomplete proxies into a direct broad-interest signal.

Current coverage

Wikimedia Pageviews API quarterly article-view trends, Stack Overflow tag-volume context, a current Google autocomplete suggestion snapshot, a compact attention/demand summary, and a search-interest companion view are included as public-interest and query-intent proxies; true search-volume history still needs Google Trends or another search provider.

Best next source

Google Trends or another search-interest provider

Collection step

Import Google Trends or an equivalent search-interest export for WordPress, WordPress developer, Shopify, Wix, Squarespace, and Webflow.

Target tables

search_interest_quarterly search_query_suggestions search_query_intent_summary

Done when Normalized quarterly search series for WordPress and peer builders, plus refreshable query-intent snapshots.
3

Job demand

Separates broad labor-market demand from narrower HN, Remote OK, Remotive, and jobs.wordpress.net proxies.

Current coverage

HN Who is hiring WordPress/WooCommerce, PHP, and agency/studio mention counts, Remote OK and Remotive current remote-job term counts, annual and quarterly WordPress Jobs board open-listing snapshots, a compact proxy-direction summary, and a job-demand companion view are included; broader multi-year labor-market demand still needs a hiring-platform time series.

Best next source

Hacker News monthly Who is hiring? threads, Remote OK and Remotive current jobs, plus hiring-platform exports

Collection step

Import a labor-market export such as Lightcast, Indeed/Hiring Lab, LinkedIn, or a comparable source.

Target tables

job_demand_quarterly wordpress_jobs_board_quarterly_snapshots

Done when Quarterly WordPress, PHP, CMS, Shopify, Wix, Squarespace, and Webflow demand rows, with the current WordPress Jobs board proxy already stored quarterly.
4

Support history

Turns the live queue snapshot into a trend that can be compared with ticket load.

Current coverage

Current report includes public support queue snapshots, quarterly Internet Archive support-view estimates from 2018 onward, resolved/unresolved/no-reply summaries, last-activity buckets, forum-level unanswered summaries, a support-load companion view, and major-plugin support-thread totals; not a full long-term topic/reply history.

Best next source

Historical WordPress.org support forum topic/reply export

Collection step

Keep the Wayback support-view estimate refreshed, then add a fuller WordPress.org topic/reply export if one is available.

Target tables

support_forum_archive_snapshots support_forum_history_quarterly

Done when Quarterly topics opened, resolved, unresolved, unanswered, reply counts, and response-age rows from a topic-level source.
5

Developer interest

Distinguishes fewer public help questions from actual developer adoption or migration.

Current coverage

Quarterly Stack Overflow tag volume, Wikimedia pageviews, npm @wordpress package downloads, Packagist Composer package snapshots, wordpress-develop PR and line review-comment activity, GitHub repository interest and topic-search snapshots, and a compact attention/demand summary are included as public attention and contribution proxies; they do not measure general search-query interest.

Best next source

Stack Exchange API question totals, Wikimedia Pageviews API, npm package downloads, GitHub PR/repository/topic/review activity, and broader developer-community sources

Collection step

Keep Stack Overflow, Wikimedia, npm and Packagist package snapshots, GitHub PR activity, GitHub topic-search breadth, and GitHub review-comment activity, then add another developer-community source if a stable public source is available.

Target tables

developer_interest_quarterly packagist_package_snapshot

Done when Developer-attention rows that combine help questions, public attention, package use, Composer ecosystem usage, and contribution activity.

Refresh workflow

After each import, update the relevant generated summary table, rerun the report artifacts, and keep the gap marked partial until the new source materially improves the signal.

Use refresh_runbook.html for the command order and data_inventory.html to confirm the new table count, row count, source hash, and gap status.