Issue #123 · important
Issue 123
What is this issue?
The article:published_time meta tag specifies when an article or blog post was originally published. This helps social platforms and search engines understand the freshness and relevance of your content.
This issue checks whether your page has the article:published_time tag implemented (for article-type content). A passing implementation must include:
article:published_time- The ISO 8601 datetime when the article was first published
Example of passing implementation:
<meta property="og:type" content="article" />
<meta property="article:published_time" content="2024-01-15T10:30:00+00:00" />
Why does it matter?
The article:published_time tag is valuable for content freshness and social sharing:
- Content freshness: Social platforms can display publish dates to users
- Chronological context: Helps users understand how recent the content is
- Search relevance: Search engines use publish dates for freshness signals
- Social sorting: Platforms may prioritize newer content in feeds
- AI Search / AEO: AI systems use publish dates to understand content timeline
Without the article:published_time tag:
- Social platforms cannot display publish dates
- Users may not know if content is current or outdated
- Missed opportunity for freshness signals
Resolving this issue improves content context in social sharing and contributes to a higher overall SEO health score by providing temporal metadata.
How to fix it
-
Add the
article:published_timetag to your HTML<head>section (for articles only):- Use ISO 8601 datetime format:
YYYY-MM-DDThh:mm:ss±hh:mm - Example:
2024-01-15T10:30:00+00:00(UTC time) - Example:
2024-01-15T10:30:00-05:00(EST time)
- Use ISO 8601 datetime format:
-
Only use for article-type content:
- Set
og:typeto "article" on pages with this tag - Don't add to homepage, product pages, or non-article content
- Set
-
Ensure accuracy:
- Use the actual first publication date
- Don't update this date when making minor edits
- Use
article:modified_timefor update timestamps
-
Test your implementation:
- Use Facebook Sharing Debugger to verify the date is detected
- Check that dates display correctly on social platforms
Examples
Example 1: Missing Article Published Time
Problematic state (what fails):
<meta property="og:type" content="article" />
<!-- Missing article:published_time tag -->
Corrected state (what passes):
<meta property="og:type" content="article" />
<meta property="article:published_time" content="2024-01-15T10:30:00+00:00" />
Example 2: Incorrect Date Format
Problematic state (what fails):
<meta property="article:published_time" content="January 15, 2024" />
<!-- Not in ISO 8601 format -->
Corrected state (what passes):
<meta property="article:published_time" content="2024-01-15T10:30:00+00:00" />
<!-- Proper ISO 8601 format -->
Example 3: Non-Article Page with Published Time
Problematic state (what fails):
<meta property="og:type" content="website" />
<meta property="article:published_time" content="2024-01-15T10:30:00+00:00" />
<!-- Should not be on non-article pages -->
Corrected state (what passes):
<meta property="og:type" content="website" />
<!-- Remove article tags from non-article pages -->
How PixyScan detects this
PixyScan checks for the article:published_time tag by:
- Fetching the page HTML after following all redirects
- Identifying article pages: Checking if
og:typeis "article" or page appears to be article-like - Parsing the
<head>section to extract the meta tag withproperty="article:published_time" - Validating presence: Checks that the tag exists on article pages
- Validating format: Ensures the value is a parseable datetime in ISO 8601 format
- Flagging the issue if the tag is missing on article pages or contains an invalid format
The detection is performed on the raw HTML response without JavaScript execution, matching how social media crawlers see your pages.