Metadata Rewrite QA

Store Positioning

Store title: Metadata Rewrite QA

Short description: Detect missing, duplicate, truncated, weak, or risky titles/descriptions and QA proposed rewrites.

SEO title: Metadata Rewrite QA — data QA, validation, and cleanup utility

SEO description: Detect missing, duplicate, truncated, weak, or risky titles/descriptions and QA proposed rewrites. Use it to validate rows, schemas, duplicates, field quality, and delivery-readiness before handing data to clients or automations.

Categories: SEO_TOOLS, DEVELOPER_TOOLS

Keywords: metadata, rewrite, qa, data qa, data/schema qa utility

Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: U2 — Data/schema QA utility
• Primary event: record-profiled at $0.00390 base
• Default max charge: $5.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. Metadata Rewrite QA: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• record-profiled: base $0.00390, GOLD $0.00312. Metadata Rewrite QA: charged when record profiled is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• issue-detected: base $0.00372, GOLD $0.00298. Metadata Rewrite QA: charged when issue detected is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• qa-report-generated: base $0.05000, GOLD $0.04000. Metadata Rewrite QA: charged when qa report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

• Audit Metadata Rewrite QA controls on a capped public sample
• Find high-priority Metadata Rewrite QA issues before release
• Validate Metadata Rewrite QA evidence from supplied pages
• Prioritize Metadata Rewrite QA fixes with severity and proof
• Export Metadata Rewrite QA QA rows for client review

Validate proposed page-title and meta-description rewrites before publication.

What This Actor Does

Metadata Rewrite QA compares current and proposed titles and descriptions. It measures length, checks preservation of required intent terms, detects duplicate peer metadata, finds repeated keywords, flags unresolved HTML entities, and identifies unsupported superlative or guarantee language.

Each dataset row includes a metadataRewriteRows evidence object with current and proposed values, exact lengths, important terms, preserved and dropped terms, intent coverage, duplicate status, and stuffed terms.

What This Actor Does Not Do

• It does not generate titles or descriptions.
• It does not estimate rankings, click-through rate, or search-engine approval.
• It does not infer peer-page uniqueness unless peerTitles and peerDescriptions are supplied.
• URL fetching does not invent proposed metadata; structured comparison fields remain required.

Best Use Cases

• prepublication QA for SEO metadata rewrites
• intent-loss checks during migrations or content refreshes
• duplicate metadata checks across supplied peer pages
• keyword-stuffing and unsupported-claim review
• client-ready metadata decision exports

Input Fields

Field	Type	Default	Notes
records	array	two built-in records	Current and proposed metadata comparisons.
urls	array	[]	Explicit source URLs; these override schema-populated defaults.
fetchUrls	boolean	false	Fetch source text when needed for traceability.
fetchTimeoutMs	integer	12000	Per-request timeout, capped at 30 seconds.
watchTerms	array	metadata terms	Terms retained in the general result summary.
includeReport	boolean	true	Writes JSON and Markdown report artifacts.
maxItems	integer	2	Result cap; maximum 50.
maxTextBytes	integer	500000	Text cap per record.

Comparison metadata fields are currentTitle, currentDescription, proposedTitle, proposedDescription, importantTerms, peerTitles, and peerDescriptions.

Example Input

{
  "records": [
    {
      "sourceId": "roof-repair-metadata",
      "sourceUrl": "https://example.com/services/roof-repair",
      "metadata": {
        "currentTitle": "Roof Services",
        "currentDescription": "Learn about our services.",
        "proposedTitle": "Roof Repair Service for Storm and Leak Damage",
        "proposedDescription": "Schedule roof repair for storm damage, active leaks, and inspection findings with an experienced local service team.",
        "importantTerms": ["roof", "repair", "storm", "leak"],
        "peerTitles": ["Roof Replacement Service"]
      }
    }
  ],
  "maxItems": 1,
  "includeReport": true
}

Output Evidence

The result reports status, severity, score, issue codes, recommendations, and normalized comparison evidence. Findings can include proposed-title-too-long, proposed-description-too-short, duplicate-proposed-title, intent-loss, keyword-stuffing, unsupported-marketing-claim, and unresolved-html-entity.

Cost Control

• Compare small batches before scaling a migration review.
• Supply only the peer metadata needed for the page group.
• Disable URL fetching when current metadata is already in the record.
• Disable report artifacts when only dataset rows are needed.

Public Task Examples

• validate rewrite intent and length before release
• find duplicate proposed titles across supplied peers
• identify keyword stuffing and unsupported claims
• prepare a metadata QA source table
• export approved and rejected rewrite rows

Limitations

Length thresholds are practical QA signals, not guarantees of search-result display. Intent coverage is lexical and depends on the supplied important terms. Rendered snippets, pixel width, localization, and search-engine rewriting require separate validation.

Source And Safety Notes

Do not include credentials or private unpublished content unless you are authorized to process it. Review flagged claims and final metadata with the content owner before publication.

Changelog

• 2026-07-10: Added intent preservation, peer uniqueness, stuffing, claim, entity, and exact-length evidence with expanded regression coverage.