A blog platform built to be found, and honest about how.

You do not need to know any of this to write a post. The defaults come from the post itself, and the editor’s Search & social panel, folded away under Advanced, is there for the times a default reads badly.

Renaming is safe. Change the slug of a live post and the old address keeps working: the free link redirects it permanently, the embed opens the post and names the new address as canonical, and the API tells your site to redirect. Drafts written with AI writing arrive with the search title and description already filled in.

There are three ways to show your posts, and they are not equal for search. The difference is whether the words of the post are in the HTML your server sends, or are added afterwards by a script.

When a post opens through the embed, the script sets the page’s title and description, adds BlogPosting data, and gives the page one canonical link: the post’s own address. It removes any canonical link already on the page so there is only one.

Google’s JavaScript SEO guidance says you can set the title, description and structured data with JavaScript, and you can set the canonical link too, as long as it does not contradict the canonical link in the page’s original HTML. Many site builders print a canonical link on every page, pointing at the page itself. On your blog page that one disagrees with the post’s.

• Remove your platform’s canonical from the blog page where it lets you. On WordPress this is a short, tested snippet that also covers Yoast and Rank Math: see CMSKite for WordPress.
• Where your platform does not let you, check one post in Google Search Console with URL Inspection to see which address Google chose. Give Google our sitemap of your posts either way.
• On Wix, pasted code runs in a frame, so the tags never reach your page. Posts are filed under your free blog link instead, and nothing is lost.

Your website does not know about posts it only shows through the embed, so its own sitemap leaves them out. We keep one for you that lists every published post at its address on your site, and drops posts you keep out of search. Name it in your robots.txt once and it stays current:

Sitemap: https://cmskite.com/b/your-blog/site-sitemap.xml

Developers get the same list from GET /v1/blog/sitemap, as JSON or ready-made XML, plus a feed in RSS, Atom or JSON. Steps for each kind of host are in the embed guide.

Assistants that answer questions from the web read pages much as search engines do, and many of their crawlers do not run JavaScript. What helps them is plain: the text in the HTML, a clear headline, an author and a date, and structured data saying which part is the article.

The free blog link and a site that renders posts with the API give them all of that in the HTML. The embed gives it to crawlers that run scripts. If being quoted by AI assistants matters to you, put your posts on your site through the API, or keep the free link public and linked. We cannot promise any assistant will quote you; nobody honestly can.

• No ranking promises. We make each post easy to read and file. Whether it ranks depends on whether it is the best answer to the search.
• “Keep out of search” on an embedded page takes the post out of the sitemaps, but the embed does not add a noindex tag to your page. On the free link the tag is added.
• The hosted sitemaps list every published post. A post marked noindex, or with its own canonical address elsewhere, is left out.
• The keywords field is for you. Search engines have ignored meta keywords for years, and we say so in the editor.

Everything on this page is included on every plan. API requests matter only if your site reads posts with code; the free link and the embed do not use them.