Article Metadata Basics: Titles, Descriptions, Slugs, and Tags

A practical guide to making article metadata accurate, consistent, and useful for readers before an article goes live.

Article metadata is the set of publishing details that identifies, summarizes, organizes, and helps present a web page. For a completed article, the essential fields usually include the page title, meta description, URL slug, category, and tags. These fields should make the article easier to understand before a reader reaches the first paragraph—not turn the page into a string of repeated keywords. A careful metadata review also catches scope mismatches, such as a title that promises a comprehensive guide when the article only provides a short checklist.

What this guide covers

What article metadata does

Think of metadata as a compact publishing brief for one URL. It gives readers a quick expectation of the page, gives editors consistent fields to review, and gives a content management system details it can use in page templates, archives, and sharing features. The article itself remains the primary source of value: metadata should accurately represent its purpose, audience, and limits.

The core fields at a glance

Write a clear SEO title

An SEO title is the title text associated with the page in publishing settings or the HTML title element. Google advises that every page have a title element and recommends descriptive, concise title text. (Influencing Title Links in Google Search | Google Search Central | Documentation | Google for Developers) It also advises against keyword stuffing and repeated boilerplate because pages need distinct text that describes their individual content. Search result title links can be truncated to fit device width, so clarity matters more than trying to reach a fixed character count.

SEO title versus H1

The SEO title and H1 can be identical, but they serve different editorial contexts. The H1 is the prominent on-page heading that begins the article for readers. The SEO title is page-level title text used outside the body as well as in the document. Keeping their central meaning aligned prevents a reader from encountering an article that appears to be about something different from what the title suggested. Use a small variation only when it makes the page easier to scan or helps the title avoid unnecessary repetition.

A reliable title-writing process

Start with the article’s specific subject, then add a useful qualifier only when it genuinely narrows the promise. Review the result against the article’s introduction and major sections before publication.

• Lead with the subject readers will recognize
• State the format or benefit when it is actually delivered, such as checklist, template, or beginner’s guide
• Use the primary topic once in a natural phrase
• Make titles distinct across articles covering related subjects
• Remove filler, exaggerated language, and repeated keyword variants
• Add a brand name only when it provides useful context and does not crowd out the article topic

Draft an accurate meta description

A meta description is a short page summary stored in a meta description element. (How to Write Meta Descriptions | Google Search Central | Documentation | Google for Developers) Google says snippets are created automatically and primarily from page content, although it may use the meta description when that description better summarizes the page. Google also says there is no length limit for a meta description, while displayed snippets may be truncated to fit device width. Treat the field as a precise summary for people, not a promise that a particular sentence will always appear in results.

A practical description formula

Write one or two plain-language sentences that answer three questions: What is the page about? Who is it for? What will the reader be able to do or understand after reading it? Include a concrete detail when it helps distinguish the article, such as the fields covered, the type of workflow, or the audience’s starting point. Avoid copying the title word for word, stacking a list of query variants, or mentioning a feature the article does not discuss.

Choose a readable, durable blog post slug

A slug is the URL-friendly path for a page or taxonomy term. Google recommends simple URL structures, readable words rather than long identifiers, and hyphens instead of underscores to separate words. It also notes that URLs are case sensitive. These are strong reasons to decide the slug deliberately before publishing and to use one lowercase, hyphen-separated style across the site.

Slug decisions that reduce confusion

The ideal slug is not necessarily a complete copy of the title. It is a concise label that remains intelligible if the title is updated later.

• Use the article’s enduring topic rather than a full sentence
• Keep meaningful words and remove filler words when doing so does not change the meaning
• Use lowercase letters and hyphens consistently
• Avoid dates, campaign labels, and temporary wording unless they are essential to the page’s purpose
• Check for an existing page with a confusingly similar slug before publishing
• Avoid changing an established slug casually; plan the technical handling of any URL change with the site owner

Use categories and WordPress tags carefully

Categories and tags are editorial organization tools, not places to repeat every possible keyword. In WordPress, posts can be assigned one or more tags, which can group posts with similar content and support navigation. (Posts Tags screen – Documentation – WordPress.org) WordPress tags do not have a parent-child hierarchy, unlike categories. A tag archive can show the posts assigned to that tag, so inconsistent near-duplicate labels can create an untidy experience for visitors and editors.

A simple taxonomy policy

Create a lightweight written policy before a tag library becomes large. The goal is consistent navigation, not maximum labeling.

• Use a category for the article’s broad, recurring editorial area
• Use a tag only when it represents a specific topic likely to connect multiple useful posts
• Choose one preferred name for a concept and reuse it exactly
• Review singular and plural variants, abbreviations, and close synonyms before creating a new tag
• Skip tags that would apply to only one article with no clear future use
• Periodically merge or retire redundant labels using the publishing workflow approved for the site

Match every field to the article’s real scope

Metadata quality is ultimately a consistency problem. A title, description, slug, category, and tags may each look reasonable in isolation while collectively describing different articles. Review them alongside the H1, introduction, headings, and conclusion. If a description says “step-by-step,” readers should find an actual sequence. If a title says “complete guide,” the article should cover the expected essentials or use a narrower label. If the slug says “wordpress-tags,” the page should substantially address WordPress tags rather than mention them once.

Avoid metadata that tries to say everything

Keyword stuffing is not a substitute for a clear topic. Repeating the same phrase in the title, description, slug, tags, and opening sentence makes the page harder to read and less distinct from related content. Select the most natural phrasing for each field, retain the same core subject, and give each field a different job: title for identification, description for summary, slug for a stable path, and taxonomy for organization.

Metadata review checklist before publishing

Use this final review in order

Review the article first, then review its metadata against the article. This order makes it less likely that polished labels will conceal an unfinished or overly broad draft.

• Confirm the H1, SEO title, and opening paragraph describe the same primary subject
• Check that the title is specific, concise, and distinct from closely related pages
• Make sure the meta description accurately summarizes the article without unsupported claims or artificial repetition
• Choose a lowercase, readable, hyphen-separated slug that reflects the durable topic
• Assign the established broad category that best fits the article
• Apply only existing, useful tags or create a new tag only when it has a clear organizing purpose
• Search the site’s existing titles, slugs, categories, and tags for confusing duplicates
• Verify that examples, calls to action, and linked resources do not expand the promise beyond the article’s content
• Preview the page in its publishing system and check for typos, cut-off text, and mismatched fields
• Record significant metadata changes so the editorial team can understand what changed and why

Illustrative worked example: correcting a scope mismatch

Illustrative example: Assume an article explains how a small business can review the title, description, slug, category, and tags of a completed blog post. It does not provide a technical audit, software comparison, or a promise of ranking improvements. The metadata should emphasize practical publishing review rather than claims the article cannot support.

Input, mapping, error, and correction

Key takeaways

• Treat metadata as an accurate introduction to a specific article, not as a list of keywords
• Write distinct, descriptive titles and avoid a fixed character-count formula
• Use the meta description as a concise summary even though displayed snippets may vary
• Choose stable, lowercase, hyphen-separated slugs that readers can understand
• Use categories and tags as a consistent navigation system, not as duplicate keyword containers
• Review every field against the article’s actual scope before publication

Frequently asked questions

What is article metadata?

Article metadata is the set of publishing details that describes and organizes a page. For a blog article, it commonly includes an SEO title, H1, meta description, URL slug, category, and tags.

How is an SEO title different from an H1?

The H1 is the prominent title readers see on the article page. The SEO title is page-level title text used in publishing settings and the document. They can match, but they should remain consistent about the article’s central subject.

How long should a meta description be?

There is no fixed maximum length for a meta description. Write a concise, accurate summary instead of chasing a character target, because displayed snippets can be truncated to fit the available device width.

Will Google always show my meta description in search results?

No. Google says snippets are generated automatically, primarily from page content, and it may use the meta description when that better describes the page.

What makes a good blog post slug?

Use a short, readable description of the enduring topic. A consistent lowercase, hyphen-separated format is a practical choice, and it aligns with Google’s guidance to use descriptive URLs and hyphens between words.

Do WordPress tags replace categories?

No. Use categories for broad editorial organization and tags for specific recurring topics. In WordPress, tags can group similar posts but do not have the parent-child hierarchy associated with categories.

How many tags should a WordPress post have?

Use only the tags that help connect the post to a meaningful, consistently named group of related articles. The right number depends on the site’s taxonomy; adding redundant or one-off tags usually does not improve organization.

Should I put the primary keyword in every metadata field?

No. Keep the central topic consistent, but write each field for its own role. Repeating exact phrases unnaturally can make titles and descriptions less useful to readers.

Prepare publishing metadata with the article

Metadata is easier to review when it is prepared alongside a complete draft and checked by a human who knows the business. SearchWeave helps businesses plan content, produce complete articles, edit them, and prepare publishing details for review. Explore SearchWeave’s AI-generated articles when you want a more organized article-to-publication workflow.

Sources and references

Influencing Title Links in Google Search | Google Search Central | Documentation | Google for Developers

How to Write Meta Descriptions | Google Search Central | Documentation | Google for Developers

Posts Tags screen – Documentation – WordPress.org