Custom API
Automatic Indexing for Custom API
HaloSEO keeps a sitemap on your own domain up to date as posts go live. Your robots.txt points at it, so new posts are found without anybody submitting them.
How HaloSEO connects to your Custom API
You give HaloSEO an API endpoint and a credential for your Custom API. The credential needs permission to create and update posts, and permission to write the sitemap file and the robots.txt file on your domain. That is the whole connection. There is no plugin to install and no account to link on a third party service. If your API uses a token, a key or a signed request, HaloSEO uses what you provide. You can revoke the credential at any time and publishing stops.
What a published post looks like on your site
HaloSEO sends the post to your Custom API as content. Your API stores it and your site renders it in your own theme. The layout, the header, the footer, the fonts and the styling all come from your site, not from HaloSEO. Readers see a normal page on your domain. The post is not a hosted page on our side and it does not carry our branding. Internal links are added to the post body so it connects to pages you already have.
What happens on Custom API that does not happen elsewhere
Because your API controls the files on your domain, HaloSEO can keep the sitemap current at the moment a post goes live. The sitemap sits on your domain and robots.txt points at it. New posts appear in it without anybody submitting a URL by hand. This is the part that matters for discovery. To be clear about the limits: HaloSEO does not ping Google, does not use IndexNow, and does not submit URLs to Search Console. It updates your sitemap and your robots.txt. Search engines still decide when and whether to crawl.
What breaks, and what happens when it does
If your API is down or returns an error, the post is not published and HaloSEO records the failure. It retries on the next run. If the credential expires or is revoked, publishing stops until you supply a new one. If the sitemap write fails, the post can still go live but the sitemap will be out of date until the next successful write. If robots.txt is changed outside HaloSEO and no longer points at the sitemap, discovery depends on whatever that file now says. We do not hide these failures. They show up so you can fix them.
Who this is not right for
This is not right for you if you want URL submission to Search Console, IndexNow pings or Google pings handled for you. HaloSEO does none of those. It is also not right for you if you cannot give API write access to your content and to the sitemap and robots.txt files, or if your site has no API and no way to add one. And it is not right for you if you need a promised ranking, position, traffic number or date. We do not control search engines and we do not promise those.
Related
the platform
the feature
same feature, another platform
How it runs, once it is connected
You do the first step. HaloSEO does the other six, on its own, every week.
- 01
Connect your website
- 02
HaloSEO researches keywords
- 03
Writes blog posts
- 04
Publishes automatically
- 05
Creates internal links
- 06
Builds backlinks
- 07
Improves rankings on Google and AI search engines