Audit SEO ialah structured investigation, bukan crawler export. Ia perlu menerangkan page mana penting, apa menghalang discovery atau usefulness, sekuat mana evidence, apa perlu diubah dahulu, siapa owner dan bagaimana result akan disahkan. Output sebenar ialah implementation system—not senarai ratusan warning.
Finding belum sedia sehingga mempunyai scope, affected URL atau template cohort, reproducible evidence, impact, confidence, recommendation, owner, risk, dependency dan verification method.
Tentukan keputusan yang perlu dibuat
Routine health check, traffic-drop investigation, pre-launch review dan WordPress migration audit ialah projek berbeza. Tentukan decision sebelum memilih tool supaya masa tidak dibahagi sama rata antara harmless notice dan business-critical failure.
Sambungkan audit kepada framework measurement SEO. Rekod baseline, intended business result, important page cohort, known change dan signal untuk verify setiap fix.
| Jenis audit | Keputusan utama | Evidence kritikal | Output |
|---|---|---|---|
| Routine health | Apa boleh merosot secara material? | Crawl, index, template, tracking trend | Maintenance backlog berpriority |
| Traffic decline | Di mana dan mengapa performance berubah? | Query/page cohort, demand, change, technical state | Hypothesis dan test berasaskan evidence |
| Pre-launch | Adakah release selamat? | Staging parity, index control, link, analytics | Go, conditional go atau no-go |
| Migration | Adakah route dan search signal dikekalkan? | Old/new inventory, redirect, Canonical, metadata | Mapping, launch dan monitoring plan |
| Content system | Apa perlu keep, improve, merge atau retire? | Intent, usefulness, evidence, overlap, outcome | Page-level content decision |
| Market expansion | Bolehkah setiap language/location journey berdiri sendiri? | Localized URL, hreflang, navigation, local proof | Market-specific plan |
Tulis audit contract
- Namakan business objective, decision owner dan audit trigger.
- Senaraikan domain, subdomain, protocol, environment, folder dan third-party journey.
- Tentukan market, language, device, template dan page role penting.
- Dokumentasikan migration, redesign, CMS change, outage, campaign dan tracking release.
- Setujui baseline period dan primary business outcome.
- Rekod access kepada Search Console, analytics, CMS, log, server, CDN dan backlink source.
- Nyatakan exclusion, assumption, privacy constraint dan unavailable evidence.
- Tentukan severity, confidence, priority, owner dan acceptance criteria.
- Tetapkan format delivery, implementation owner, review date dan escalation path.
Triage emergency sebelum full crawl
Sebelum menghabiskan masa pada metadata, pastikan site available dan selamat. Sitewide outage, accidental noindex, robots failure, broken Canonical template, expired TLS, hacked page atau manual action lebih penting daripada ratusan minor finding.
Manual Actions dan Security Issues ialah report berasingan. Manual action berkaitan policy violation yang disemak Google; security issue berkaitan hacked atau harmful behaviour. Tiada notice tidak membuktikan tiada algorithmic, quality atau technical issue.
| Emergency check | Evidence | Keputusan segera |
|---|---|---|
| Availability | Representative HTTP, DNS, TLS dan uptime | Escalate 5xx, timeout, certificate atau DNS failure |
| Index control | Rendered robots meta, X-Robots-Tag, robots.txt | Stop unintended sitewide block |
| Canonical template | Source/rendered samples | Stop rollout jika priority page menuju tempat lain |
| Security | Security Issues, Safe Browsing, server/CMS | Contain, clean, patch, kemudian request review |
| Manual action | Search Console Manual Actions | Fahami scope dan policy dahulu |
| Tracking | GTM/GA4 dan conversion test | Jangan diagnose behaviour daripada broken collection |
Simpan baseline sebelum membuat perubahan
Export atau rekod URL inventory, redirect, status, title, description, heading, Canonical, robots, hreflang, structured data, Sitemap, internal link, Search Console cohort, analytics event dan qualified outcome sebelum fix.
Untuk migration atau redesign, simpan juga screenshot representative template dan old routing rules. Tanpa baseline, team tidak boleh membezakan fix, regression atau demand change.
- Public crawl dan render sample daripada important template.
- XML Sitemap, robots.txt, HTTP header dan status inventory.
- Search Console Page Indexing, Performance, Manual Actions, Security dan Crawl Stats.
- GA4/GTM implementation, key-event definition dan test record.
- Old/current URL inventory serta redirect rules.
- Page role, market, language, template dan business-priority map.
- Backlink dan brand mention dengan source URL.
- Change log, release history, incident dan stakeholder input.
Bina URL inventory daripada beberapa source
Crawler hanya menemukan laluan yang boleh dicapai dari starting point. Gabungkan live crawl dengan Sitemap, analytics landing page, Search Console page, server log jika perlu, CMS/database export, backlink destination, paid campaign URL dan old-site inventory.
Normalize scheme, hostname, trailing slash, casing, fragment, tracking parameter dan decoded form sebelum compare. Simpan raw evidence supaya normalization tidak memadam perbezaan routing sebenar.
| Source | Apa ditemui | Blind spot |
|---|---|---|
| Crawler | Linked live URL dan technical state | Orphan dan blocked path |
| Sitemap | Declared preferred indexable inventory | Omitted atau stale URL |
| Search Console | Google-known dan performing URL | History dan sample limit |
| Analytics | Measured landing page | No-traffic dan untracked URL |
| CMS/database | Published dan scheduled record | Route luar CMS |
| Backlink | Externally referenced current/retired URL | Internal inventory |
| Server log | Actual crawler dan user request | Retention dan parsing complexity |
Audit discovery, crawl dan server access
Google Cari melibatkan discovery, crawling, rendering, indexing, Canonical selection dan serving. Mulakan pada gate terawal yang rosak. Jika important page tiada normal crawlable link atau server gagal, introduction rewrite bukan first priority.
Gunakan panduan crawling dan indexing serta panduan Sitemap dan robots. Robots.txt mengawal crawl; ia bukan reliable removal tool.
| Finding | Evidence | Action | Verification |
|---|---|---|---|
| Important orphan | CMS/Sitemap/GSC URL tiada dalam crawl | Tambah crawlable link atau retire | Re-crawl dari intended hub |
| Redirect chain | A → B → C | A terus ke final equivalent | HTTP test semua source |
| Soft 404 | 200 dengan missing/error experience | Truthful status atau useful page | Live fetch dan inspection |
| 5xx/timeout | Repeatable response atau log cohort | Fix capacity, app atau dependency | Monitor endpoint dan log |
| Blocked resource | Robots dan rendered difference | Allow resource diperlukan | Rendered inspection |
| Crawler trap | Unbounded filter/calendar/parameter | Constrain route dan discovery | Crawl pattern dan log trend |
Banding source HTML, rendered HTML dan user experience
Untuk JavaScript page, compare initial response, browser-rendered DOM, Google rendered view jika ada dan actual mobile task. Google boleh render JavaScript, tetapi rendering ialah processing stage berasingan.
Semak title, robots, Canonical, hreflang, heading, main content, link, structured data, error state, lazy media dan pagination pada source serta rendered state.
| Comparison | Soalan | Failure |
|---|---|---|
| HTTP → source | Adakah usable content dikembalikan? | Empty app shell atau error 200 |
| Source → rendered | Adakah script mengekalkan signal? | Canonical atau robots berubah |
| Desktop → mobile | Adakah content dan function equivalent? | Mobile buang service detail |
| Fresh load → interaction | Bolehkah content dicapai tanpa prerequisite tersembunyi? | Link hanya selepas filter |
| Success → error | Adakah unavailable state truthful? | Failed API hasilkan indexable empty page |
Audit indexability, Canonical dan duplicate cluster
Indexability ialah intended state, bukan target 100%. Login, internal search, duplicate filter, expired campaign dan alternate copy boleh betul-betul unindexed. Cari important page yang excluded secara salah dan low-value URL yang included tanpa tujuan.
Canonical signal termasuk redirect, rel=canonical, Sitemap dan consistent internal link. Semua perlu menuju genuinely equivalent preferred URL.
| Page state | Control | Evidence | Decision |
|---|---|---|---|
| Preferred public | 200, indexable, self-consistent | Inspection dan live crawl | Keep dan strengthen discovery |
| Duplicate equivalent | Canonical atau redirect | Content/purpose equivalence | Consolidate signal |
| Private/sensitive | Authentication | Anonymous access denied | Jangan rely pada robots |
| Public bukan untuk Cari | Noindex ketika crawlable | Rendered directive | Keep hanya jika user perlu |
| Removed with replacement | Permanent redirect | Map dan destination QA | Update internal reference |
| Removed tanpa replacement | 404 atau 410 | Response dan navigation cleanup | Truthful removal |
Audit template sebelum isolated URL
Satu template defect boleh menjejaskan ratusan URL: duplicate title, missing content, wrong Canonical, inaccessible accordion, weak breadcrumb, oversized hero atau duplicate schema. Group finding mengikut template dan page role.
Sample best/worst performing, newest/oldest, indexed/excluded, multilingual, mobile dan edge-case URL bagi setiap important template.
| Template | Sample | Emphasis |
|---|---|---|
| Service | High-value dan low-impression | Intent, proof, CTA, local/language fit |
| Artikel | Pillar, supporting, new, declining | Usefulness, source, author, internal link |
| Category/hub | Large dan small group | Discovery, description, pagination, overlap |
| Portfolio/case study | Client dan owned project | Verifiable scope, media, claim, conversion |
| Utility/tool | Success, empty dan error state | Function, crawl route, result indexability |
| Localized | Equivalent dan non-equivalent | Translation, navigation, hreflang, Canonical |
Audit architecture dan internal link ikut journey
Architecture perlu membantu user memahami kedudukan, langkah berkaitan dan commercial/support destination. Crawl depth ialah diagnostic—not universal rule.
Gunakan site architecture dan internal linking. Crawlable link biasanya memerlukan anchor element dengan href; script-only click bukan pengganti reliable.
| Check | Soalan | Action |
|---|---|---|
| Hierarchy | Adakah page placement jelas? | Clarify hub, label, breadcrumb dan navigation |
| Depth | Adakah priority page terlalu dalam? | Cipta relevant route |
| Anchor | Adakah text menjelaskan destination? | Baiki vague atau forced anchor |
| Orphan | Adakah indexable page tiada normal link? | Link, merge, noindex atau retire |
| Overlap | Adakah beberapa URL menjawab intent sama? | Differentiate atau consolidate |
| Dead end | Adakah logical next step? | Tambah relevant path—not random links |
Map search demand kepada page job
Technically perfect page masih boleh gagal kerana menjawab task salah. Group query mengikut intent, audience, market, language, funnel stage dan format. Compare ranking/landing URL dengan page yang sepatutnya memenuhi need.
Gunakan keyword research dan search intent untuk memilih service page, guide, category, comparison, tool, local page atau tiada URL baru.
| Pattern | Diagnosis | Decision |
|---|---|---|
| Wrong page ranks | Architecture atau intent overlap | Clarify role, link, content atau consolidate |
| Impression tetapi weak click | Snippet, position mix, feature atau mismatch | Inspect priority SERP |
| Traffic tanpa outcome | Informational demand atau weak journey | Match CTA dengan intent |
| Tiada impression | Eligibility, demand, competition atau usefulness | Diagnose earliest failed gate |
| Banyak similar page | Keyword-variant expansion | Keep hanya distinct task |
Nilai usefulness, evidence dan accountability content
People-first guidance bertanya sama ada content membantu intended audience, menunjukkan useful experience atau knowledge, mempunyai tujuan jelas dan membolehkan user mencapai goal. Jangan cipta E-E-A-T score.
Review Who, How dan Why. High-impact topic perlukan expertise, current source, limitation dan review owner yang lebih kuat. AI assistance bukan automatic problem; scaled unoriginal content untuk manipulate ranking ialah policy risk.
| Dimension | Evidence | Weak signal |
|---|---|---|
| Audience/purpose | Clear intended user dan task | Dibuat hanya untuk traffic |
| Original value | Decision, example, test, data, experience | Summary page lain |
| Accuracy | Current primary source dan correction path | Unsupported/stale claim |
| Creator | Relevant author/reviewer | Generic byline |
| Method | Disclosure jika process matters | Automation menyembunyikan unreliable production |
| Maintenance | Review trigger dan truthful date | Date berubah tanpa material update |
Audit on-page signal dan search presentation
Title, heading, opening, description, image dan link perlu menjelaskan page purpose. Metadata tidak boleh menggantikan inaccessible, duplicate atau unhelpful page.
Gunakan panduan Title Tag, Meta Description, Heading, Image SEO dan Content Refresh.
- Satu primary task dengan distinct secondary need.
- Accurate title dan H1 tanpa forced repetition.
- Opening answer cepat.
- Heading membentuk logical outline.
- Claim, example, image dan source menambah information.
- Link mempunyai descriptive context.
- Metadata sepadan dengan visible content.
- CTA sesuai dengan stage dan mobile.
- Author, business, contact dan policy tepat.
Audit structured data sebagai eligibility layer
Structured data menerangkan visible information dan mungkin membolehkan eligible Cari feature. Ia bukan general ranking switch; valid markup tidak menjamin rich result.
Semak syntax, feature eligibility, visible-content match, property dan policy. Jangan tambah self-serving review, invented rating, false price atau unverifiable entity claim.
| Layer | Soalan | Evidence |
|---|---|---|
| Syntax | Boleh parse? | Validator dan source/render |
| Eligibility | Google support feature dan page type? | Current documentation |
| Content match | User boleh lihat maklumat? | Rendered comparison |
| Identity | Name, URL dan entity konsisten? | Organization/person/page record |
| Policy | Claim misleading atau melanggar guideline? | Manual review dan policy map |
Audit page experience tanpa mengejar satu score
Core Web Vitals mengukur real-world loading, responsiveness dan visual stability melalui LCP, INP dan CLS. Gunakan field data untuk population evidence dan lab trace untuk root cause.
Review mobile usability, secure delivery, overlay, readable layout, stable interaction, accessible navigation, form dan error recovery. Ikut workflow Core Web Vitals.
| Area | Evidence | Jangan |
|---|---|---|
| LCP/INP/CLS | Field distribution + reproducible trace | Optimize satu lab run |
| Mobile journey | Real-device task dan content parity | Hide core content |
| Payload | Image, font, script, third party | Compress sehingga unusable |
| Overlay | First-visit access | Block primary task |
| Accessibility | Keyboard, label, contrast, focus, semantic | Anggap automated score complete proof |
Audit multilingual dan local journey berasingan
English, Bahasa Melayu dan Simplified Chinese perlu berguna secara sendiri. Semak translation, terminology, navigation, Canonical, reciprocal hreflang, internal link, metadata dan next step.
Untuk local SEO, verify Business Profile eligibility, public detail, genuine review, service-area truth dan location page yang mempunyai distinct local value.
| Layer | Soalan | Failure |
|---|---|---|
| Translation | Natural dan preserve intent? | Machine text dengan broken term |
| Navigation | Selected language kekal? | Unexpected English link |
| Canonical | Genuine equivalent self-preferred? | Semua language Canonical ke English |
| Hreflang | Live equivalent reciprocal? | Missing return atau invalid code |
| Local proof | Location/service claim real? | Cloned city page atau fake address |
| Conversion | Boleh contact team sesuai? | Broken/untranslated CTA |
Audit backlink, mention dan policy risk dengan evidence
Review exact source page, context, destination, anchor, acquisition pattern dan relevance. Third-party authority atau toxic score ialah vendor metric—not Google fact.
Pisahkan editorial link, mention, partnership, paid placement, UGC, hacked link dan deliberate manipulation. Gunakan backlink audit serta Disavow decision guide.
| Evidence | Maksud | Action |
|---|---|---|
| Relevant editorial mention | Source memilih untuk cite | Preserve destination |
| Paid/sponsored | Commercial placement | Qualify dan disclose |
| Tool-labelled toxic | Vendor opinion | Manual inspect |
| Confirmed manipulation | Pattern + ownership evidence | Stop, remove/qualify, assess Disavow |
| Link ke retired URL | External demand ke old route | Restore, equivalent redirect atau truthful status |
Audit migration sebagai high-risk system
Migration audit bermula dengan complete old-to-new inventory. Kekalkan established URL jika boleh. Jika URL berubah, map setiap valuable old URL kepada genuinely equivalent destination dan update link, Canonical, Sitemap serta monitoring.
Google mengesyorkan perubahan major dilakukan satu demi satu jika praktikal. Domain move, CMS, redesign, content rewrite, tracking dan URL restructure serentak mengurangkan diagnostic clarity.
- Freeze old URL, metadata, Canonical, hreflang, status dan performance inventory.
- Map one-to-one equivalent dan flag URL tanpa honest replacement.
- Test new site dan pastikan production block tidak terbawa ke launch.
- Update link, Canonical, hreflang, schema, navigation dan Sitemap.
- Test redirect untuk loop, chain, pattern dan intent.
- Verify GTM, GA4, form, phone, WhatsApp dan consent.
- Launch, inspect URL dan monitor old/new crawling serta traffic.
- Kekalkan redirect untuk user dan system.
Gunakan first-party QA evidence
Audit credible memisahkan reusable process daripada project evidence. Current SEOWithJack build merekod verification sebenar—not anonymous traffic gain. Nombor ini versioned dan boleh berubah.
| Verified evidence | Result | Membuktikan | Tidak membuktikan |
|---|---|---|---|
| HTML documents | 710 | Generated inventory discan | Semua page layak rank |
| Indexable/Sitemap | 459 / 459 | Declared inventory align | Google wajib index semuanya |
| Image references | 14,663 | Build image QA dijalankan | Visual usefulness atau ranking |
| JSON-LD blocks | 710 | Setiap HTML ada checked block | Rich result display |
| Preserved WordPress article URLs | 27 | Original route matched/redirected | Tiada future fluctuation |
| Redirect-map rows | 53 | Migration decision documented | Setiap 410 perlu jadi 301 |
Diagnose traffic change ikut pattern
Decline boleh datang daripada technical, security/manual action, migration, demand, competition, page change, measurement failure atau ranking-system change. Mulakan dengan shape dan cohort.
Compare period setara dan segment page, query, country, device, language, Cari type serta role. Gunakan confirmed Google timeline tanpa menganggap tarikh sebagai cause.
| Pattern | First check | Jangan assume |
|---|---|---|
| Sitewide sudden loss | Availability, robots, noindex, Canonical, security, tracking | Content-quality issue |
| Slow cohort decline | Demand, competition, intent, content, link | Satu technical flag |
| Impression stable; click fall | CTR, position mix, snippet, feature | Indexing failure |
| GSC stable; GA4 fall | Tag, consent, redirect, classification | Cari traffic hilang |
| Only migrated URLs | Redirect, Canonical, link, Sitemap | General algorithm update |
| One language/market | Hreflang, navigation, demand, localization | Whole domain affected |
Pisahkan severity dan implementation priority
Severity menerangkan consequence jika finding benar. Priority juga mengambil kira reach, business importance, confidence, effort, risk, dependency dan reversibility.
Jangan sembunyikan judgement dalam mystery health score. Paparkan logic dan dokumentasi override.
| Dimension | Soalan | Scale |
|---|---|---|
| Impact | Apa boleh improve? | Low / medium / high / critical |
| Reach | Berapa important URL/journey? | Single / cohort / template / sitewide |
| Confidence | Seberapa reproducible? | Hypothesis / supported / confirmed |
| Effort | Development/content/data? | Small / medium / large |
| Risk | Boleh harm traffic/user/data? | Low / medium / high |
| Dependency | Apa perlu dahulu? | Owner / approval / platform / data |
| Reversibility | Boleh rollback? | Easy / controlled / difficult |
Tukar finding menjadi implementation ticket
| Field | Required | Contoh |
|---|---|---|
| Finding | Exact condition | Migrated article redirect dua hop |
| Scope | URL/cohort/template/market | 27 legacy routes |
| Evidence | Reproducible test | Crawler + redirect map |
| Impact | User/search/business effect | Slower path dan maintenance |
| Recommendation | Specific end state | Direct permanent redirect |
| Owner/dependency | Team + prerequisite | Developer + approved map |
| Risk/rollback | Failure + recovery | Routing regression + restore rules |
| Acceptance | Testable state | Single hop, correct destination |
| Verification | Bila dan bagaimana | Staging, production HTTP, re-crawl |
| Status | Lifecycle | Backlog → ready → doing → QA → verified |
Release fix melalui risk-based QA
Copy correction boleh focused review; sitewide Canonical, robots, routing, template, schema atau tracking perlukan staging, sample, automated checks, rollback dan monitoring.
Ticket complete apabila acceptance criteria pass—not apabila code merged.
| Risk | Contoh | Minimum QA |
|---|---|---|
| Low | Typo, source, isolated alt | Editorial review + live check |
| Medium | Title pattern, link, content merge | Staging sample, link, Canonical, mobile |
| High | Robots, noindex, Canonical, redirect | Automated inventory, rollback, monitoring |
| Critical | Domain/CMS migration, routing/tracking rebuild | Full gate, owner sign-off, old/new monitoring |
Ikut audit sequence praktikal
- Define decision, scope, stakeholder dan baseline.
- Triage availability, index control, security, manual action dan tracking.
- Assemble multi-source URL dan evidence inventory.
- Crawl dan sample source, rendered, mobile, success dan error state.
- Map discovery, access, index, Canonical dan Sitemap.
- Review template, architecture, link, intent dan page role.
- Evaluate content usefulness, evidence, accountability dan maintenance.
- Inspect page experience, schema, multilingual/local dan external trust.
- Compare affected Cari/business cohort dengan change log.
- Validate finding dan alternative explanation.
- Prioritize impact, reach, confidence, effort, risk dan dependency.
- Bina owned ticket dengan acceptance criteria.
- Test ikut risk, launch, re-crawl, inspect dan monitor.
- Archive evidence, decision, result dan review trigger.
Nyatakan apa yang audit tidak boleh buktikan
- Crawler warning ialah lead—not automatic harm evidence.
- Search Console bukan complete web log.
- URL Inspection tidak mewakili setiap page atau ranking condition.
- Valid page, Sitemap atau indexing request tidak guarantee index/rank.
- Canonical ialah signal; Google boleh pilih lain.
- Valid structured data tidak guarantee rich result.
- Lab score tidak mewakili setiap real user.
- E-E-A-T bukan exposed single score.
- Third-party traffic, authority, keyword dan toxicity ialah estimate.
- Correlation dengan release/update bukan causation proof.
- Fix semua finding tidak guarantee traffic atau recovery.
- Audit time-bounded; site dan market terus berubah.
Elakkan audit failure biasa
- Crawl tanpa business question dan scope.
- Anggap semua non-indexed URL sebagai error.
- Lapor semua warning tanpa validation.
- Satu health score sebagai conclusion.
- Audit homepage atau desktop sahaja.
- Fix metadata sebelum sitewide access/Canonical.
- Ubah stable URL untuk cosmetic cleanliness.
- Cipta page bagi setiap keyword/city variation.
- Toxic score sebagai proof dan mass Disavow.
- Salahkan update kerana tarikh hampir.
- Report tanpa owner, safeguard atau verification.
- Mark complete sebelum production criteria pass.
Soalan lazim
Berapa kerap audit SEO?
Monitor availability, security, indexing dan tracking secara berterusan. Buat deep audit sekitar major launch, migration, unexplained decline dan material business change.
Tool audit SEO mana terbaik?
Tiada satu tool ialah audit. Crawler, Search Console, analytics, render test, CMS/server evidence dan business record menjawab soalan berbeza.
Perlukah setiap crawler warning diperbaiki?
Tidak. Validate condition, scope dan potential impact terhadap important user, URL, Cari eligibility atau measurement.
Berapa lama audit mengambil masa?
Bergantung pada inventory, template, market, JavaScript, migration, access dan question. Small-site audit boleh mengambil hari; multi-market migration memerlukan staged review.
Apa deliverable audit?
Decision summary, evidence archive, prioritized finding, scope, ticket, owner, acceptance criteria dan verification plan.
Bolehkah audit guarantee ranking recovery?
Tidak. Audit boleh membaiki supported problem dan reduce risk; demand, competition, ranking system dan timing kekal tidak pasti.
Adakah site: search complete index audit?
Tidak. Ia rough discovery check. Gunakan Search Console, URL Inspection dan own inventory.
Perlukah semua excluded page diindex?
Tidak. Duplicate, private page, internal search, filter dan obsolete URL mungkin betul-betul excluded.
Adakah server log diperlukan?
Tidak untuk semua small site. Ia berguna apabila crawler behaviour, large inventory, response pattern atau migration tidak boleh dijawab oleh source lain.
Siapa implement audit finding?
Assign pemilik sistem: developer, content owner, designer, analytics, server admin atau stakeholder. Auditor mendefinisikan end state dan verification.
Rujukan rasmi
- Google Cari Essentials
- Google Cari: how crawling, indexing, and serving work
- Google Cari technical requirements
- Google Cari: maintaining your website SEO
- Google Search Console: URL Inspection
- Google Search Console: Page indexing report
- Google Search Console: Crawl Stats report
- Google Cari: build and submit a Sitemap
- Google Cari: robots meta and X-Robots-Tag
- Google Cari: Canonical methods
- Google Cari: JavaScript SEO basics
- Google Cari: mobile-first indexing best practices
- Google Cari: localized versions and hreflang
- Google Cari: crawlable links and anchor text
- Google Cari: helpful, reliable, people-first content
- Google Cari spam policies
- Google Cari: site moves with URL changes
- Google Cari: Core Web Vitals
- Google Cari: page experience
- Google Cari: structured data guidelines
- Google Cari Central: debug Cari traffic drops
- Google Search Console: Manual Actions report
- Google Search Console: Security Issues report
Kongsikan domain, Search Console access/export, change history, migration record dan business priority. Jack boleh memisahkan verified risk daripada tool noise.
Evolusi Ranking Google: Daripada PageRank ke Modern Cari Systems2 September 2026
Kandungan AI dan SEO Google: Apa Dibenarkan, Apa Dianggap Spam dan Cara Publish2 September 2026
Google Florida Update 2003: Fakta, Teori dan Lesson SEO2 September 2026