Map your source fields to the audit schema
pSEO Guard recognizes a small set of common CSV aliases automatically. Use the standard field names when you can; aliases are a convenience, not a replacement for a clear source schema.
Last updated
Use the standard fields when possible
The clearest input uses the same field names shown in the CSV Schema. That keeps exports, audits and future publishing steps easier to trace.
- url, title, h1
- meta_description, target_keyword, canonical
- word_count, parent_url, indexable
- content_text, template_id
Common aliases are normalized automatically
You do not need to rename every familiar spreadsheet heading before import. The current audit recognizes common alternatives and maps them to the standard field.
- path or page_url → url
- seo_title or meta_title → title
- heading or heading_1 → h1
- keyword, primary_keyword or intent → target_keyword
- parent or hub_url → parent_url
- content, body, body_text or text → content_text
- template or page_type → template_id
What is not mapped automatically
The current CSV audit does not provide a custom drag-and-drop field mapper. A source column with an unfamiliar name remains its own column, so rename it to a supported field or alias before relying on that value in the audit.
Check the result after import
If an expected check is missing, confirm the source column was recognized before assuming the page passed. Missing body content, hierarchy or intent data can change which checks are measurable.
Next action
Use the rule reference when a page needs a decision, or continue through the Docs in order.