Content Update Policy

Why content freshness matters

A tool guide is only useful if it matches the tool as it exists today. When someone follows step-by-step instructions to compress a PDF and the buttons do not match what the guide describes, that is a broken promise. Outdated content wastes people's time and erodes trust. We take content freshness seriously because we know people rely on our pages to accomplish real tasks — submitting assignments, sending job applications, or meeting deadlines.

Browser technology changes constantly. New JavaScript APIs become available, old ones get deprecated, and browser behavior varies across versions. A guide written two years ago might reference a browser feature that no longer works the same way. Our update process accounts for these changes.

Update frequency by content type

We do not apply a one-size-fits-all review cycle. Different content types have different rates of change, and our review schedules reflect that:

Tool pages (active tools)

Tool pages are the most important content on our site and receive the most frequent review. Each tool page is reviewed every time the underlying tool receives an update. This is a hard rule — no tool ships without a corresponding content review. The review checks that:

All instructions match the current interface
Screenshots and descriptions reflect the current design
Supported file types and limitations are accurately listed
Tips and best practices are still relevant
Any new features are documented

In practice, this means high-traffic tools like our PDF merge, word counter, and resume checker are reviewed multiple times per year. Less frequently updated tools might be reviewed once or twice annually, but always within six months of the last review.

Blog posts and guides

Educational content like "How to Write a Resume That Passes ATS Screening" or "Understanding PDF Compression Levels" is reviewed quarterly. At each quarterly review, we verify:

Statistics and data points are still current
Recommendations align with current best practices
External references (like ATS software names or PDF standards) are still accurate
The advice still reflects how our tools actually work

If a blog post references specific software versions, browser features, or industry standards that have changed, we update the post immediately rather than waiting for the quarterly cycle.

FAQ pages

FAQ content is reviewed semi-annually. Since questions and answers tend to be more stable than procedural guides, a six-month cycle keeps them current. However, if we receive multiple user questions that suggest an FAQ answer is outdated, we review it immediately.

Policy and legal pages

Pages like our privacy policy, terms of service, and this content update policy are reviewed semi-annually or whenever our practices change. If we modify how we handle data, process files, or operate the site, the corresponding pages are updated to reflect those changes.

Category and hub pages

Pages that aggregate tools by category (like our PDF tools or student tools hubs) are reviewed quarterly. These pages need to reflect our current tool lineup — if we add a new tool, it should appear on the relevant hub page promptly. If a tool is retired or substantially changed, the hub page is updated accordingly.

Accuracy verification process

Reviewing content is not just about checking whether the text is still technically correct. Our verification process includes several steps:

Interface verification: We open the tool and walk through every step described in the content, confirming that each action produces the described result.
Screenshot verification: We check whether screenshots still match the current interface. If the UI has changed, we retake screenshots and update the content.
Link verification: We verify that all internal and external links still work and point to the correct destinations. Broken links are fixed or removed.
Claim verification: We re-test any functional claims (compression ratios, processing speeds, accuracy rates) to ensure they still hold with current browser versions and tool code.
Completeness check: We verify that new features or changes are documented and that nothing has been missed.

What triggers an immediate update

Beyond scheduled reviews, certain events trigger immediate content updates:

Tool interface changes: Any change to buttons, labels, menus, or workflow triggers an immediate documentation review.
New browser support: When we add support for a new browser or OS, we update relevant content to reflect that.
User-reported errors: When someone tells us that a page's instructions do not work, we treat that as a high-priority bug. We verify the report, fix the content, and respond to the reporter.
Industry standard changes: When PDF specifications update, ATS software changes parsing behavior, or accessibility standards evolve, we review all affected content.
Legal or regulatory changes: If privacy laws, accessibility requirements, or other regulations change in ways that affect our tools or documentation, we update immediately.

User feedback handling

User feedback is one of our most valuable inputs for identifying content that needs attention. We handle feedback through a structured process:

Reports of outdated content: When someone tells us a page's information is wrong or outdated, we verify the report within 48 hours. If confirmed, we fix the content within one week and respond to the reporter.
Suggestions for improvement: Feedback about unclear instructions, missing information, or confusing language is logged and addressed during the next scheduled review cycle. High-impact suggestions may trigger an immediate update.
Feature-related feedback: When users report that a tool feature works differently than documented, we prioritize verifying and correcting the documentation. This feedback also informs our tool development priorities.
Accessibility feedback: Reports of accessibility barriers are treated as high-priority issues and addressed within the same timeline as bug reports.

We do not guarantee that all feedback will result in changes, but we do guarantee that all feedback is read and considered. Every piece of feedback is logged in our tracking system and categorized by type, priority, and affected content.

How we track reviews

Every content page in our system has a "last reviewed" date and a scheduled next review date. Our editorial calendar flags pages approaching their review date, and no page goes more than two weeks past its scheduled review without explicit justification. We maintain an internal changelog for each page documenting what was reviewed, what changed (if anything), and why.

This tracking is not just internal busywork. We display the "last reviewed" date on every tool page and blog post so you can see exactly when the content was last verified. Transparency about our review process is part of the policy.

Version history and changelogs

For major content updates — anything that changes the meaning, advice, or significant details of a page — we add a visible note at the bottom of the page. This note includes what was changed and approximately when. For tool pages, major updates are tied to tool version releases, making it easy to understand what changed and why.

Minor corrections (fixing a typo, updating a broken link, refreshing a screenshot) are made without annotation. These changes do not affect the substance of the content and do not warrant a formal changelog entry.

Our changelog approach is designed to balance transparency with readability. We want users to be able to understand what has changed without being overwhelmed by a list of every minor edit. Significant changes get documented; routine maintenance does not.

Notification of changes

We do not currently send notifications when content is updated, but we are considering adding this feature for users who want to stay informed about changes to specific pages. In the meantime, the "last reviewed" date on each page serves as a simple indicator of content freshness.

For changes to policy and legal pages (privacy policy, terms, disclaimer), we update the "last modified" date prominently and note the nature of the change at the top of the page. We believe users should always be able to understand what has changed in legal documents that affect their rights.

Retiring content

Occasionally, a tool or guide is no longer relevant. When we retire content, we do not delete the page silently. Instead, we either redirect the URL to a more relevant page or add a clear notice explaining that the tool or guide is no longer available and why. This prevents broken bookmarks and helps users find what they need instead of hitting a dead end.

If a tool you used on ToolsKit has disappeared and you cannot find an explanation, contact us and we will point you in the right direction.