Content Freshness Checker

Content Freshness Checker helps you investigate whether a webpage exposes usable publication and modification date signals and how old the strongest detected freshness reference is. Enter a public webpage URL or paste HTML/content to inspect published dates, modified dates, JSON-LD signals, time elements, visible date patterns, and HTTP Last-Modified information when available.

What Is Content Freshness?

Content freshness is about how recently information was published or meaningfully updated. It matters most for pages where facts, recommendations, prices, procedures, software details, regulations, products, or other time-sensitive information can change.

A date alone does not prove that content is current. A page can display a recent modified date while still containing outdated information, and an evergreen resource can remain useful for a long period without frequent changes.

PKCapra’s Content Freshness Checker therefore focuses on detectable date signals rather than claiming to determine the factual freshness of a page.

What Does the Content Freshness Checker Analyze?

The current tool can inspect:

• Publication date metadata
• Modification date metadata
• JSON-LD datePublished
• JSON-LD dateModified
• Other detected JSON-LD date fields
• Article publication metadata
• Article modification metadata
• <time datetime> elements
• Visible date patterns
• HTTP Last-Modified when a public URL is fetched
• Publication-versus-modification consistency
• Future-date anomalies
• Estimated content age
• Overall freshness diagnostic signal
• Priority findings

The report also shows the detected date signals, their source, the selected freshness reference, and the analysis method.

Why Content Freshness Matters

Some information changes quickly.

Examples include:

• Software documentation
• Search engine guidance
• Product specifications
• Prices
• Financial information
• Government procedures
• Legal or regulatory information
• Technical standards
• Travel information
• Current recommendations
• News and current events

Other content can remain useful for years with little or no change.

The important question is therefore not simply:

How old is this page?

A better question is:

Does the information still accurately serve the reader’s current need?

The Content Freshness Checker helps with the first part of that investigation by identifying available date signals.

How the Content Freshness Checker Works

1. Enter a public webpage URL

Enter an HTTP or HTTPS URL.

For example:

https://example.com/article

When a URL is supplied, PKCapra fetches the public HTML and examines the returned response.

The URL analysis can also inspect the HTTP Last-Modified response header when the server provides one.

2. Or paste HTML/content

You can paste HTML or page content instead of providing a URL.

This is useful for reviewing draft or locally prepared content before publishing it.

The pasted-content input has a maximum size of 200,000 characters.

3. Run the analysis

PKCapra extracts recognizable date signals from the supplied content.

It checks common metadata, structured data, time elements and visible date patterns.

4. Review the freshness report

The report provides:

• Freshness Signal
• Grade
• Summary
• Published date
• Modified date
• Age
• Number of detected date signals
• Date Signals table
• Freshness Checks
• Priority Findings
• Source Summary

This gives you both the overall diagnostic and the evidence behind it.

Publication Dates and Modification Dates

The tool distinguishes between publication and modification signals.

Published date

A publication date represents when content was initially published.

For structured data, Google’s Article documentation defines datePublished as the date and time when an article was first published. Google recommends using ISO 8601 date/time information and timezone information when providing this property. :contentReference[oaicite:0]{index=0}

Modified date

A modification date represents a later change to the content.

Google’s Article structured data documentation defines dateModified as the date and time when the article was most recently modified and recommends providing it when applicable. :contentReference[oaicite:1]{index=1}

The PKCapra tool can detect these signals when they are exposed in supported metadata or structured data.

A detected modified date does not prove that every statement on the page was reviewed.

JSON-LD Date Signals

Many pages expose article information through JSON-LD structured data.

The analyzer examines JSON-LD for common date properties such as:

• datePublished
• dateCreated
• dateModified
• uploadDate

For Article structured data, datePublished and dateModified are recognized properties in Google’s documentation. :contentReference[oaicite:2]{index=2}

PKCapra reports the detected signal and its source so you can see whether the date came from JSON-LD rather than assuming that every date on a page has the same meaning.

Meta Date Signals

The analyzer also checks common metadata patterns for publication and modification dates.

Examples include article publication and modification metadata.

These signals can be useful when a page exposes dates in metadata even when the visible page does not make the date immediately obvious.

A metadata date should still be compared with the actual content and other available signals.

<time datetime> Signals

The tool checks <time> elements that expose a datetime attribute.

For example:

<time datetime="2026-09-20">September 20, 2026</time>

This provides a machine-readable date signal that can be included in the report.

The presence of a <time> element does not automatically establish that it represents publication or modification. The tool reports the detected signal so it can be reviewed in context.

Visible Date Signals

The analyzer also looks for recognizable dates in visible content.

For example:

September 20, 2026

or:

2026-09-20

Visible dates can provide useful evidence, but they may represent many things besides publication or modification.

A date in an article could refer to an event, study, historical period, product release, example, or other information.

This is why visible date detection is treated as a signal rather than automatic proof of content freshness.

HTTP Last-Modified

When analyzing a public URL, PKCapra can inspect the HTTP Last-Modified response header when it is supplied by the server.

This provides a server-level date signal.

It should not automatically be interpreted as the date when the article’s editorial content was last reviewed. Server behavior varies, and the header can represent the modification time of the HTTP resource rather than a specific editorial update.

The tool therefore reports it as a separate signal.

How the Freshness Reference Is Selected

When usable dates are detected, the analyzer prioritizes a modification signal when one is available.

If no usable modification date is detected, it can use the publication date as the freshness reference.

The report explicitly indicates whether the selected reference is based on a modified or published signal.

If no usable date is detected, the tool reports that freshness cannot be reliably estimated from its available date signals.

Understanding Content Age

The tool calculates an approximate age in days from the selected freshness reference.

For example:

Reference	Approximate Age	Interpretation
Modified date	20 days	Recent detected signal
Modified date	210 days	Review may be useful
Published date only	500 days	Older reference; modified date unavailable
No usable date	Unknown	Freshness cannot be estimated from dates

Age is a diagnostic measurement, not a universal definition of stale content.

A technical tutorial may remain useful for years, while a page about current software features can become outdated much faster.

Understanding the Freshness Signal

PKCapra calculates a deterministic Freshness Signal from the detected age and available date signals.

The current diagnostic scale uses these age bands:

Detected Reference Age	Base Diagnostic Signal
0–30 days	100
31–90 days	95
91–180 days	85
181–365 days	70
366–730 days	50
731–1,095 days	30
More than 1,095 days	15

When only a publication date is available and no modification signal is detected, the implementation applies a diagnostic reduction.

A detected future date produces a very low diagnostic signal and is separately reported as an anomaly.

These thresholds are PKCapra heuristics, not Google’s freshness thresholds.

Understanding the Grades

The current tool uses these diagnostic grades:

• Fresh Signal: 85–100
• Generally Current: 65–84
• Review Recommended: 45–64
• Potentially Stale: below 45
• Unknown Freshness: no usable date reference

These labels describe the detected date signals.

They do not mean that Google considers a page fresh, stale, high quality, or low quality.

What a Fresh Signal Means

A fresh signal means the selected detectable date reference is relatively recent according to PKCapra’s diagnostic thresholds.

For example, a page with a recently detected dateModified signal may receive a strong freshness signal.

You should still inspect the actual changes.

A recent date without substantive content updates is not the same thing as a meaningful editorial review.

What an Older Signal Means

An older signal means the selected detectable reference is further in the past.

This is a reason to investigate, particularly for pages covering information that changes frequently.

Ask:

• Have the facts changed?
• Have screenshots or interfaces changed?
• Have product specifications changed?
• Have links or procedures changed?
• Have regulations changed?
• Have software versions changed?
• Does the page still answer the user’s current question?

What “Unknown Freshness” Means

Unknown freshness means the analyzer did not detect a usable publication or modification date.

This does not prove that the content is old.

Some pages simply do not expose recognizable date metadata.

It means the tool does not have enough date evidence to calculate a meaningful age from its supported signals.

Missing Modified Date Does Not Automatically Mean Stale

A page may expose a publication date without exposing a modified date.

The tool reports this as a limitation of its freshness diagnostic.

It does not conclude that the content is outdated.

Google’s Article structured data documentation describes dateModified as a recommended property when applicable, rather than a universal requirement for every article. :contentReference[oaicite:3]{index=3}

If a page has no modified date, inspect the actual content before deciding whether an update is required.

Date Consistency Checks

The analyzer checks whether a detected modification date appears earlier than a detected publication date.

For example:

• Published: September 20, 2026
• Modified: September 15, 2026

This produces a date-consistency warning because the detected modification date precedes publication.

The correct response is to investigate the page’s metadata rather than assuming the page is technically broken.

Future-Date Anomalies

The tool also looks for dates that appear materially in the future.

A future date can result from:

• Incorrect structured data
• Incorrect CMS settings
• Timezone problems
• Template errors
• Incorrect visible text
• A legitimate future event date

Therefore, a future-date finding is an investigation signal rather than proof of manipulation or an SEO violation.

Practical Example

Imagine an article reports:

• Published: January 15, 2026
• Modified: September 10, 2026
• Current analysis date: September 27, 2026

The tool can use the modification date as the freshness reference and calculate an approximate age from that date.

The report might then show:

• Published: January 15, 2026
• Modified: September 10, 2026
• Age: approximately 17 days
• Date signals: multiple detected
• Freshness Signal: strong diagnostic signal

The important editorial question remains:

What actually changed on September 10?

If only the visible date was changed without reviewing the content, the date itself does not establish factual freshness.

How to Use Freshness Findings

When the analyzer identifies an older reference, use this workflow.

Review time-sensitive information

Check facts that can change over time.

Examples include:

• Prices
• Product specifications
• Software features
• URLs
• Regulations
• Procedures
• Statistics
• Screenshots
• Platform policies
• External resources

Review the original publication date

Determine whether the content is intentionally evergreen.

A long-lived reference guide may not require frequent rewriting.

Review the modification date

If a modified date exists, determine whether it corresponds to a substantive update.

Update changed information

Where facts have genuinely changed, revise the relevant sections rather than merely changing the date.

Recheck the page

After updating the content, run the checker again to verify that the expected date signals are exposed correctly.

Content Freshness vs. Date Freshness

These are not the same thing.

Date freshness asks:

How recent is the detected publication or modification signal?

Content freshness asks:

Is the information itself still accurate and useful?

PKCapra’s tool primarily measures the first question.

The second requires human review and, where appropriate, authoritative current sources.

Content Freshness and Search

Freshness can matter differently depending on the query and subject.

A current event or rapidly changing topic naturally has different freshness requirements from an evergreen explanation of a stable concept.

Google’s documentation also makes clear that Search systems use multiple signals and that there is not a single universal page-experience signal. :contentReference[oaicite:4]{index=4}

Do not interpret the PKCapra Freshness Signal as a standalone prediction of search rankings.

Content Freshness and Structured Data

Structured data can expose publication and modification information.

Google’s Article documentation specifically defines datePublished and dateModified for article structured data and recommends accurate date information where applicable. :contentReference[oaicite:5]{index=5}

The PKCapra analyzer can detect these fields, but detecting valid structured data does not mean the underlying content is necessarily current.

Structured data should accurately describe the page rather than being changed merely to create a newer-looking date.

A Practical Content Update Workflow

For pages that may need refreshing:

1. Run the Content Freshness Checker.
2. Record the detected publication and modification signals.
3. Review the actual content age.
4. Identify time-sensitive claims.
5. Check current authoritative sources where necessary.
6. Update information that has genuinely changed.
7. Remove obsolete information.
8. Review examples, screenshots and links.
9. Verify the page’s publication and modification metadata.
10. Re-run the checker.
11. Review the final page from the reader’s perspective.

For broader on-page diagnostics, use the On-Page SEO Checker.

Related SEO Checks

Freshness is only one part of maintaining useful content.

You may also want to review:

• On-Page SEO Checker for broader page-level signals.
• SEO Content Score for content structure and readability diagnostics.
• Topic Coverage Analyzer for checking supplied topics and supporting subtopics.
• Semantic Keyword Analyzer for analyzing terminology and recurring phrase patterns.
• Broken Link Checker for identifying broken links that can make otherwise useful content less reliable.
• HTTP Status Checker for checking HTTP response status.

Use each tool for the specific diagnostic it provides rather than treating one score as a complete SEO assessment.

Common Content Freshness Problems

The page has an old publication date

An old publication date does not automatically mean the page needs to be rewritten.

First determine whether the subject is evergreen and whether the information remains accurate.

The page has no modification date

A missing modification signal limits this particular diagnostic, but it does not establish that the content is outdated.

Review the page itself.

The modification date is recent but the information is old

This can happen when a CMS or editor changes the modification timestamp without a substantive content update.

Check the actual revision.

The modification date is before publication

This usually indicates a metadata or date-handling issue that should be investigated.

A future date is detected

Review structured data, visible date text, CMS configuration and timezone handling.

The date may be legitimate if it refers to a future event rather than the publication or modification of the page.

Why You Should Not Change Dates Without Updating Content

Changing a visible date without making meaningful content changes can create a misleading freshness signal.

The better workflow is:

Review → Update where necessary → Verify → Publish

rather than:

Change date → Assume content is fresh

The purpose of a freshness review is to maintain useful and accurate information, not simply to make an old page appear newer.

Limitations

The Content Freshness Checker is a deterministic date-signal diagnostic.

It does not:

• Verify factual accuracy.
• Determine whether an article was substantively updated.
• Compare the current page against an older version.
• Determine whether a topic has changed since publication.
• Query Google Search’s internal freshness systems.
• Predict search rankings.
• Guarantee eligibility for any search feature.
• Determine the correct update frequency for a page.
• Automatically decide whether content should be rewritten.
• Crawl an entire website.
• Verify every date on a page’s semantic meaning.
• Guarantee that a detected date is the editorial publication or modification date.

The current implementation analyzes common publication/modification metadata, JSON-LD date fields, <time> elements, visible date patterns, and HTTP Last-Modified when a public URL is fetched.

Date extraction is therefore a diagnostic representation of the signals exposed by the analyzed source.

Privacy and Processing

When a public webpage URL is supplied, PKCapra sends a server-side request to retrieve the page HTML for analysis.

The URL analysis may also inspect the HTTP response headers, including Last-Modified when available.

When HTML or content is pasted, the supplied content is sent to the same analysis endpoint for processing.

The current pasted-content limit is 200,000 characters.

The tool does not require an AI API, paid freshness database, or external SEO API.

For PDF reporting, the analysis results are rendered in the browser using the client-side PDF libraries used by the tool. The generated PDF is based on the displayed report.

Do not submit confidential or sensitive content unless you understand the implications of processing it through the service.

Frequently Asked Questions

What does a Content Freshness Checker do?

It identifies detectable publication and modification date signals and estimates the age of the strongest available freshness reference using a deterministic diagnostic heuristic.

Does Content Freshness Checker know whether my content is actually up to date?

No. It detects date signals. It cannot verify whether the information itself remains accurate.

What date signals does PKCapra detect?

The tool can detect publication and modification metadata, JSON-LD dates, <time datetime> values, visible date patterns and HTTP Last-Modified information for public URL analysis.

Does the tool check datePublished and dateModified?

Yes. The analyzer examines common JSON-LD and metadata date fields, including datePublished and dateModified.

What if no date is detected?

The tool reports Unknown Freshness because it cannot calculate a reliable age from the supported date signals.

This does not prove that the page is outdated.

Is an old page automatically bad for SEO?

No. Whether content needs updating depends on its subject, the user’s needs, and whether the information remains accurate and useful.

Does changing the date make content fresh?

No. A changed date does not establish that the underlying information was meaningfully reviewed or updated.

Why is my modified date missing?

The page may not expose a recognizable modification signal, or its CMS may not publish one in a format the analyzer detects.

Why is the HTTP Last-Modified date different from my article date?

HTTP Last-Modified is a server response signal. It can represent the resource’s HTTP-level modification rather than the editorial date of an article.

Why did the tool report a future date?

The page may contain a future event date, incorrect metadata, a timezone issue, or another date value that appears to be in the future. Review the reported source before taking action.

Does a Freshness Signal of 100 mean Google considers the page fresh?

No. The 0–100 signal is a PKCapra heuristic based on detected date information. It does not reproduce Google’s internal freshness systems.

Can I use Content Freshness Checker for old evergreen articles?

Yes. It can help identify the available date signals and age, but you should decide whether an evergreen article actually needs updating based on its subject and factual accuracy.

Which PKCapra tools should I use with Content Freshness Checker?

For a broader content review, combine it with the Topic Coverage Analyzer, Semantic Keyword Analyzer, SEO Content Score, and On-Page SEO Checker.