1. Scheduled review cadence
| Content type | Review cadence | Owner |
|---|---|---|
| Pillar tutorials (Playwright, Selenium, JMeter…) | Every 6 months | Editor + tool-owner reviewer |
| Interview Q&A hubs | Every 4 months | Interview panel reviewer |
| Salary guides & job-market reports | Every 3 months | Data lead |
| Tool reviews & comparisons | Every 12 months (or on major release) | Editor who tested |
| Career & freelancing playbooks | Every 6 months | Career editor |
| News / opinion posts | Not re-updated (dated) | Original author |
| Legal & trust pages | Every 12 months + on material change | Founder |
2. Out-of-cycle triggers
An article is pushed to the top of the queue immediately when any of these happen:
- Major tool release — Playwright 2.x, Selenium 5, Postman engine rewrite, Node LTS bump.
- Breaking API change — Deprecation warnings visible on the reader's console.
- Pricing / licence change — free tier removed, seats capped, T&Cs rewritten.
- Salary shift > 10% — Levels, Glassdoor, LinkedIn, and government data agree.
- Interview format shift — new round, new coding platform, take-home replaces live.
- Reader-reported inaccuracy confirmed by our Fact Checking Policy.
- Google helpful-content update that changes our signal reading.
3. Signals we monitor
- Tool GitHub releases & RSS feeds for every product we cover.
- Vendor changelogs and pricing pages via a weekly diff cron.
- Google Search Console CTR & position drops (> 20% week-on-week).
- Comment threads and community reports on the QA Hangar.
- Broken-link crawls (weekly) and structured-data validation (nightly).
4. What “updated” means
We don't bump the “Last updated” date for typo fixes. A real update means at least one of:
- New version tested end-to-end and code samples re-run.
- New section added, or an outdated section rewritten.
- Salary / benchmark numbers refreshed from primary sources.
- Reviewer sign-off from the named reviewer for that content type.
5. Retire & redirect
An article is retired when:
- The tool is EOL and has no upgrade path (Selenium IDE Firefox, Protractor).
- The topic is fully absorbed by a better pillar page.
- Traffic sits below noise for 12 months AND no reader has cited it.
When we retire, we 301 redirect the URL to the closest live page, log it in the Corrections Log, and preserve the historical version on request for anyone who cited it.
6. Transparency to the reader
Every article surfaces its publication date, last-updated date, and named reviewer at the top of the page. Salary guides and tool comparisons additionally expose the data source and version. Where an article is intentionally frozen (opinion, obituary of a tool, historical retrospective), we label it “Archive — not updated”.
3, 4, 6, or 12 months by content type.
Major releases jump the queue.
Code samples pinned to the version tested.
Typos don't bump the date.
Material changes logged publicly.
Dead tools 301 to living guides.