Ilé ìmọ̀
Ṣẹda bọ́tìnì API Render kan ki o si so ọna mọọ, ki awọn aaye aimi rẹ le kọ lati inu ibi ipamọ rẹ lori akọọlẹ Render ti ara ẹni.
Connecting your own Render account lets you publish a static site to your Render account from your Zinn® dashboard. You own the project and the bill; we handle the deploy, the custom domain and the DNS records.
A Render account, and a connected GitHub, GitLab or Bitbucket account holding the site's code — Render builds sites from a repository and cannot accept an uploaded build. Render's free static sites allow commercial use.
In the Render Dashboard, open Account Settings, find API Keys and create a new key. Render shows the full key once, when it is created; copy it then.
Open Integrations in your dashboard and choose Connect an account. Pick Static hosting (Netlify, Vercel) as the group and Render as the account, fill in API token, and press Connect account.
We test what you paste before anything is saved. A key that does not work is never stored, and the answer says what was wrong with it. A key that works is kept encrypted in our secrets vault — never in our database — and is never shown again, not even to you.
target. Render builds from a repository — it has no way to accept an uploaded build — so the site's code must come from a connected GitHub, GitLab or Bitbucket repository. Connect one first if you have not.
and trigger deploys. The domain's page shows any DNS record Render needs.
The site cannot be created. Check that a repository account is connected and that Render itself can reach the repository — Render may ask you to authorise its own access to your Git provider in its dashboard.
The key was revoked. Render keys stay valid until revoked; if yours was, create a new one.
It says the key was rejected. Almost always one of three things: a space or a line break copied with it, a key that has expired, or a key that was revoked or regenerated after you copied it. Create a fresh one and paste it again.
It connects, but something later fails. The key authenticates but lacks a permission the action needs. Create a new key with the permissions listed above, then disconnect the old connection and connect the new key.
Open Integrations, find the account and press Disconnect. That deletes the stored key at once. Anything that was using it stops at its next action, and the screens that depended on it say so rather than failing quietly.
Disconnecting does not undo what was already done — records, deployments or settings we changed on your account stay as they are. If you think the key itself may have leaked, also revoke it at the vendor; disconnecting removes our copy, not theirs.
Ohun ti a ti n kọ nipa iṣẹ-ayelé, SEO ati ṣiṣe awọn aaye ni iwọn.
Bẹ́ẹ̀ ni agbára ìgbékalẹ̀ ojú-wọ́ ṣe ń nípa lórí ìtọ́kasí ati iye ọna àjápọ̀ ní ọdún 2026: mímú kí àwọn ojú-ewé wà nínú atọ́ka, ṣíṣàyẹ̀wò àwọn àgbàgbà agbègbè wẹ́bù kí o tó kọ́ sórí wọn, ìkọ́ṣẹ́ ọna àjápọ̀ láìfi àlùmọ́lì sílẹ̀, àti òtítọ́ nípa ohun tí agbára ìgbékalẹ̀ le ṣe àti ohun tí kò le ṣe fún SEO.
Ka ifiweranṣẹ naa →Àkọsílẹ aṣeṣe fún WordPress tó yára tí ó sì ní ààbò: ìpamọ́ ipele-súpà, ìpamọ́ ohun ti a ṣe fún ojú-wọ́ọ̀bù kọ̀ọ̀kan, díẹ̀ lára àwọn plọ́gìnnì (plugins) tí ó tọ́ láti lò, bíbójútó ẹ̀rọ náà kí ó wà ní ìsinsìnyí, àti àwọn ojú-ewé WooCommerce tí o kò gbọdọ̀ pamọ́ rárá.
Ka ifiweranṣẹ naa →Ohun tí ó ń yàgbà fún gbígbé ojú òpó wọ́lú tí ó dára kò si sí pẹ̀lú pẹpẹ ìṣàkóso ni — ìṣípòpadà, àwọn àfẹòmọ́, ìpín sọ́tọ̀, ìkójọpọ̀ gidi àti ìwọ̀n gidi — àti bí a ṣe lè ṣe ìdájọ́ rẹ̀ kí o tó ṣe ìpinnu.
Ka ifiweranṣẹ naa →Atilẹyin wà lori gbogbo eto, ile-iṣẹ wa wa ni ṣiṣi fun iwọn wákàtí 24 lojoojumọ, o si le kọwe si wa ni eyikeyi ninu awọn ede wa ti o jẹ 58 — a o sọ fun ọ ni ede rẹ.
Kan si àtìlẹyìn → Gbogbo àpilẹ̀kọ →