Getting started with Google Search Console for an Iranian site

Search Console shows how Google sees the site. In the first week after launch: verify ownership, submit the sitemap, watch 5xx and 404, and request indexing for important pages. KGSM runs this on client projects. The practical path lives in SEO; if the error is server or code, involve web programming. Coordinate domain access via contact.

This guide — Getting started with Google Search Console for an Iranian site — is written from KGSM delivery work: scoped first versions, staged releases, and support after handoff.

Audience, risk, and how KGSM works

An Iranian site owner who just launched or has no Search Console and wants index and errors from week one

Without Search Console, SEO is guesswork: money pages stay out of the index, staging gets in, and a 500 lingers for weeks.

KGSM treats verification, sitemaps, and error watch as SEO start, on kgsm.ir or on your domain.

Verify domain ownership the right way

For an Iranian site, DNS verification on the domain itself is best so www, apex, and paths stay under one property. If you only verify a URL prefix, the other version may be seen separately and the data stays incomplete. Put the record on the real DNS, not an expired panel. Give Console access to a company account, not the designer’s personal Gmail that will be gone tomorrow. KGSM writes this at the start of SEO so you are not locked after handoff. If the domain is new, wait for DNS to propagate; an early Validate fails and the team thinks Google is blocked. Redirect http to https before two properties exist. Keep the ownership document in the contract. If several people need reports, give a limited role rather than sharing a password.

Verify with DNS on the domain, not only a URL prefix. Only www was verified and apex data stayed incomplete until DNS was fixed.

Submit Persian and English sitemaps

sitemap.xml should list live canonical URLs only — not thank-you pages, duplicate filters, or admin links. If you have fa and en, submit separate maps or declare both in a sitemap index. After each new block — service, article, product — update the map and submit again in Console; once a year is not enough. KGSM ties the sitemap to language path and lastmod so crawl does not stick on stale pages. If a shop has thousands of SKUs, split the map so one error does not kill the file. Remove noindex URLs from the map. After submit, watch discovered versus indexed weekly. If discovery is high and index is low, inspect quality or crawl budget instead of publishing twenty more similar pages. robots.txt must not block the sitemap; that mistake is common after over-eager security rules.

The sitemap included the admin panel and Google discovered hundreds of junk URLs. Give Console access to a company email, not the contractor’s Gmail.

Run coverage, 5xx, and 404 every week

Read the Page indexing report like a support ticket, not a score. Check server errors in the browser and server logs first, then Validate Fix in Console. 301 high-traffic 404s to a replacement; you can ignore zero-traffic 404s. Soft 404 is a «not found» body with status 200 — fix that in web programming. KGSM puts the first week of these reports in the contract. If Iranian hosting drops at times, add uptime monitoring because Console reports late. Request indexing for a money page after the fix. Do not request removed URLs. Block staging with robots or basic auth so it is not indexed. A lingering 500 on a money page costs more than ten new articles and needs an owner the same day.

Strip noindex and thank-you URLs from the sitemap. Staging was indexed and a «test» title appeared in results.

Index money pages and read the queries

Indexing requests are limited; spend them on home, services, and pillar articles, not archive tags. After two to four weeks open Performance: query, page, country, device. Iranian sites are usually mostly Iran and mobile; if desktop dominates in Console, the mobile page may not be indexed. Change titles on URLs with impressions and no clicks. KGSM lines this loop up with content monthly. If a service page will not index, check canonical and noindex before writing a new article. Keep the KGSM brand and kgsm.ir stable in titles and links so a brand query lands in the right place. To set up Console on your site, tell contact who holds DNS so verification does not stall. Match the report to real inquiries so SEO is not only a screenshot.

A payment-page 500 sat in Console for three weeks because nobody read server logs. Resubmit the same week you publish a new service.

Fix 500s on the server first, then Validate Fix. Indexing requests were spent on archive tags and the service page was seen late.

The designer’s Gmail was closed and Console ownership was lost. Block staging from the index.

Save indexing requests for money pages. Only www was verified and apex data stayed incomplete until DNS was fixed.

The sitemap included the admin panel and Google discovered hundreds of junk URLs. Each month turn high-impression low-click queries into title changes.

Implementation checklist

• Verify with DNS on the domain, not only a URL prefix.
• Give Console access to a company email, not the contractor’s Gmail.
• Strip noindex and thank-you URLs from the sitemap.
• Resubmit the same week you publish a new service.
• Fix 500s on the server first, then Validate Fix.
• Block staging from the index.
• Save indexing requests for money pages.
• Each month turn high-impression low-click queries into title changes.

Field scenario 1

Only www was verified and apex data stayed incomplete until DNS was fixed.

Verify with DNS on the domain, not only a URL prefix.

Field scenario 2

The sitemap included the admin panel and Google discovered hundreds of junk URLs.

Give Console access to a company email, not the contractor’s Gmail.

Field scenario 3

Staging was indexed and a «test» title appeared in results.

Strip noindex and thank-you URLs from the sitemap.

Field scenario 4

A payment-page 500 sat in Console for three weeks because nobody read server logs.

Resubmit the same week you publish a new service.

Field scenario 5

Indexing requests were spent on archive tags and the service page was seen late.

Fix 500s on the server first, then Validate Fix.

Field scenario 6

The designer’s Gmail was closed and Console ownership was lost.

Block staging from the index.

Related KGSM pages

Continue with KGSM services: سئو و بهینه‌سازی, طراحی سایت. Related reading: راهنمای سئو سایت فارسی ۱۴۰۵ — چک‌لیست عملی برای رتبه گوگل, Core Web Vitals برای سایت فارسی: LCP، CLS، INP. For a scoped estimate, use the contact form.

When you apply this on a live team, write it as an operating rule, not a slide: Verify with DNS on the domain, not only a URL prefix. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Give Console access to a company email, not the contractor’s Gmail. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Strip noindex and thank-you URLs from the sitemap. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Resubmit the same week you publish a new service. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Fix 500s on the server first, then Validate Fix. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Block staging from the index. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Save indexing requests for money pages. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Each month turn high-impression low-click queries into title changes. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Only www was verified and apex data stayed incomplete until DNS was fixed. Then assign an owner and a review date so the rule survives the first busy week.