Persian SEO

Tie recommendations to actual URLs and user value. Apply the evidence policy. Read SEO sources to verify guidance and audit method for Persian variants, technical checks and reporting.

For Iranian projects, read the Iranian commerce and local-page checks section in the task reference when money, payments, phone/SMS, fulfillment or local dates affect the request. Apply relevant checks only; keep other Persian regions and the user’s scope intact.

For choosing or reviewing blog content, read editorial decisions. Use available project/connector evidence first and separate writing quality, search demand and measured outcomes.

Workflow

1. Bound the audit. Establish page set, audience, geography, engine and goal. Note access to live/rendered pages, robots responses and owner-supplied performance/indexing data. Finish with scope and access limits.
2. Inspect technical evidence. Check relevant status, crawl controls, indexing directives, canonical targets, rendered content, links and mobile accessibility. Check language variants only where they exist. Distinguish markup from the engine's selected canonical/indexing state; the latter requires engine data. Read current official guidance for recommendations affected by changing policies.
3. Research Persian intent. Use supplied query data and accessible search evidence; record date, engine, locale and collection limits. Cluster meaningful spelling/register variants, including ی/ک and نیم‌فاصله, by intent. Check URLs/Unicode encoding without bulk-renaming. Trends shows relative interest; retain original query spelling in evidence. Finish with supported clusters and labeled demand gaps.
4. Prioritize changes. Give URL, evidence, benefit, severity, confidence and fix. Assess unique value before proposing catalog/location pages at scale. Structured data must be supported, eligible and truthful to visible content; verify currency/schema values rather than inventing a toman code. For local or seasonal content apply the audit method’s service-area and calendar checks. Separate technical blockers from content hypotheses.
5. Plan verification. Name post-change checks and baseline/window. Compare equivalent periods and note seasonality, campaigns or tracking changes. For implementation requests, make authorized changes and verify affected pages. Audit completion does not authorize publishing or requesting credentials.

Deliverable and completion

Return scope, prioritized URL-level findings, confirmed facts versus hypotheses, fixes, unverified checks and measurement plan. Each finding needs evidence; current indexing, traffic and demand claims need appropriate data. Separate Persian-specific considerations from universal engine guidance.