Ama-signals ekhasini

Isiqinisekiso se-Canonical

Ngenisa ikhasi le-URL. Siyithola kusuka kumsekeli wethu futhi siyishicilele isihloko, isichazamazwi se-meta, i-canonical, amarobots meta nama-hreflang tags, ngemikhawulo yobude kanye nokubheka ukuthi i-canonical ibhekisa ngokwayo futhi iphelele.

Indlela yokuhlola ikhasi le-meta ne-canonical tags

Izinqumo ezine, akukho ukubhalisa. Ukuhlolwa okuphelele kuqhutshwa ku-server-side.

1

Ncamashi ikhasi le-URL

Ngenisa i-URL ephelele yekhasi ofuna ukulihlola, kufaka phakathi indlela.

2

Siyithola futhi siyihlukanise

Isisebenzisi sethu sicela ikhasi, silandela ukudluliswa, futhi sihlela isiphetho, ngakho-ke ubona i-canonical ku-URL ephelile, hhayi ikhophi egcinwe.

3

Funda iziphetho

Ithegi ngayinye ithola i-chip yokudlulisa/ukuphuma: isihloko nesichazamazwi sobude, ukubhekisa kwe-canonical, amarobots meta, ne-hreflang coverage.

4

Ukuxazulula futhi uphinde ubheke

Lungisa noma yisiphi isiphawuli esiphawulwe ngeflegi, sebenzisa, futhi uphinde uqhube ukuhlolwa ukuze uqinisekise ukuthi i-canonical ibhekisa ngokwayo futhi iphelele.

Izinto ezizohlolwa yilesi sihlola

Ama-signals ekhasini avame ukuvala isizinda, esigabeni esisodwa.

📏

Isihloko nesichazamazwi

Isilumkisa uma isihloko noma isichazamazwi se-meta side kakhulu ukuveza noma sincane kakhulu ukusebenziseka ku-SERPs.

🔗

Canonical self-reference

Iqinisekise ukuthi i-canonical iphelele, i-host eyodwa futhi ikhombisa ikhasi layo. Yi-duplicate-content killer.

🤖

Amaroboti meta

Ifaka i-robots meta directive futhi ifaka i-noindex engalindelekile ezosusa ikhasi kusuka ku-search.

🌐

Ukugqugquzela kwe-Hreflang

Ibonisa i-hreflang eshintshayo kanye namabhukwana lapho i-x-default ingekho kumakhasi akhuluma izinhlelo eziningi.

Imibuzo ebuzwa kaningi

I-canonical ebhekisa kuyo ikhombisa ikhasi le-URL. Uma ikhombisa indawo ethile noma isebenzisa indlela ephathelene, i-Google ingakhetha i-canonical ehlukile futhi ibike 'I-Duplicate, Google chose a different canonical', ekhipha ikhasi lakho kusuka kwisithotho.
Njengemithetho yethumb, izihloko ezingaphezu kuka-50 kuya ku-60 izibonakaliso kanye nokuchaza okungaphezu kuka-120 kuya ku-160 izibonakaliso zibonisa ngaphandle kokuncipha kuningi SERPs. Umkhangeli utshela uma i-tag ide kakhulu noma incane kakhulu.
Yebo. Sibheka i-robots meta value futhi sicela noindex ngokucacile, njengoba i-noindex engalindelekile iyisizathu esivamile sokuthi ikhasi lifihle ngokucophelela ekutholeni.
Uma ushicilela ikhasi ngemilimi eminingi, i-x-default itshela ama-search engines ukuthi inguqulo efanele ukuhlinzeka abasebenzisi abakhona abazosebenzisa i-locale engafani nanoma iyiphi yezindlela zakho ezihlukile. Umhlola uphawula uma i-hreflang ikhona kodwa i-x-default ingekho.
Abathuthukisi

Sebenzisa ku-pipeline yakho

Lo mhloli usebenza ngokuphelele ku-server-side. Uthumela i-URL, i-backend yethu ithola ikhasi, ilandela izixhumanisi, iqoqa ikhanda, futhi iphinde Bona ama-plans →

Umthuthukisi we-API

Sebenzisa ngokuzenzakalelayo

Yonke into itholakala nge-REST API eqinisekisiwe eyodwa ku-Pro ne-API. Intambo ifakwe ku-CI yakho, CMS, noma ama-dashboards.

curl -X POST https://seo.bike/api/v1/meta-check \ -H "Authorization: Bearer sk_live_yourkey" \ -H "Content-Type: application/json" \ -d '{"url": "https://example.com/"}'
Ok
{ "ok": true, "result": { ... } }
Thola isithonjana se-API → I-metered, per-call pricing. I-free tier yethuluzi elixhumanayo phezulu.
Khangela ikhasi ngalinye lendawo yakho, hhayi elinye ngasikhathi sinye
Pro ixhuma Google Search Console, ithola yonke ikhasi Google elahlekile, yonke ikhasi elahlekile kanye nekhasi ngalinye elingaphakeme, futhi ibhala ukuthi yini ukuxazulula ngayinye.
Bona ukuthi i-Pro isebenza kanjani