Connect Dev.to to LazySEO
LazySEO can post articles to your account on DEV (dev.to) through the DEV API. DEV is a community site, not your own website: posts there build reach on DEV, but they don't add pages to your domain.
Last reviewed October 1, 2026.
Before you start
- A DEV (dev.to) account.
- Keep in mind that LazySEO does not set a canonical URL on DEV posts. If the same article is also published on your own site, add the canonical URL to the DEV post yourself, or use DEV as the only destination for those articles.
Step by step
1Generate a DEV API key
- On dev.to, open Settings and go to Extensions.
- Under DEV Community API Keys, enter a description such as
LazySEO. - Click Generate API Key and copy the key.
2Open the integration form in LazySEO
- Open your project in LazySEO.
- In the left sidebar, under Settings, click Integrations.
- Click Add Integration.
- In the window that says "Choose the type of integration you want to add.", click DEV.to.
3Save the integration
Fill in the fields as described in the table below, leave Enabled switched on (disabled integrations are skipped during publish) and click Add integration.
Fill in the LazySEO form
Labels below match the DEV.to form in LazySEO. Fields marked required must be filled in before you can save.
- Namerequired
Any name that helps you recognise this connection. Only shown inside LazySEO.
Example:
DEV account- API Keyrequired
The API key you generated on dev.to.
Example:
a1B2c3D4e5F6g7H8i9J0k1L2- Enabled
Leave on. When it is off, LazySEO skips this integration when publishing.
Test the connection
- Right after you save, the window shows Test the connection: click Run quick test. You can test again at any time from the integration card with Test.
- Quick test ("Check endpoint is reachable") signs in to the DEV API with your API key and reads your own DEV account. Nothing is created.
- On the card's Test menu, Full test ("Send a test blog post (draft)") sends a real test article titled "[TEST] LazySEO Test Article" with the slug
lazyseo-test-article. On DEV it is created as an unpublished draft. Delete it from your DEV dashboard once you have checked it. - If a test fails, LazySEO shows the reason it got from your platform (for example a rejected key or a missing permission). Check it against the troubleshooting section below, click Edit on the card to fix the field, and test again.
What gets published
| What | How LazySEO handles it |
|---|---|
| Title | The article title. |
| Body | The article's Markdown, sent as the post's Markdown body (body_markdown), which is the format DEV is written in. A first heading that only repeats the title is dropped, because DEV shows the title itself. Articles you edited in the LazySEO editor are stored as HTML and are passed through as HTML, which DEV renders inside the Markdown. |
| Status | Published. The Full test creates an unpublished draft. |
| Description | The meta description. |
| Tags | Up to four article topics, converted to DEV's tag format: lowercase, letters and numbers only, no duplicates. For example "SEO Strategy" becomes seostrategy and "Next.js" becomes nextjs. |
| Cover image | The article banner image URL. |
| Post URL | LazySEO saves the URL DEV returns as the article's published URL. |
| Updates | If the same article is published again to the same integration, LazySEO updates the existing post instead of creating a second one. If you deleted the post in DEV in the meantime, the update fails with HTTP 404 instead of creating a new post (see troubleshooting). |
| Unpublishing | Unpublishing an article inside LazySEO does not remove it from your site. Delete or unpublish the post in your platform if you need it gone. |
Troubleshooting
HTTP 401 ("DEV.to rejected the API key").
The API Key is wrong or was revoked. Generate a new one in Settings → Extensions.
HTTP 422 with a message about a field.
DEV rejected part of the article; the message says which field. Tags are already converted to DEV's format, so this is usually about the title, the cover image URL or the body. Contact support@lazyseo.io if it keeps happening.
HTTP 429 ("rate limit reached").
DEV limits how many articles can be posted in a short time. Wait a few minutes and use Retry on the article.
Publishing an article again fails with HTTP 404.
The post was deleted on DEV after LazySEO first published it. LazySEO tries to update that post and DEV can't find it; for DEV it does not yet create a new post automatically. Email support@lazyseo.io with the article's name and we will help.
Frequently asked questions
Will posting to DEV help my own website rank?
Not directly. DEV posts live on dev.to. They can send readers to your site through links in the article, but they do not add pages to your domain.
Still stuck?
Email support@lazyseo.io with the error message from LazySEO and we'll help you connect.