Kennext scans your site and shows you every issue that is costing you visibility with Google and AI assistants. Connect HubSpot, and Kennext writes the fixes you approve to your pages and blog posts. Every change can be undone from Kennext.
Kennext writes 29 kinds of fixes for you once you approve them, including:
Page titles that are missing, too long, too short or duplicated.
Page descriptions that are missing, too long, too short or duplicated.
The official address of a page (the canonical tag).
Open Graph tags and structured data (JSON-LD), each written as its own marked Kennext block in the page's head, so the rest of your head code is left as it is.
Redirects for pages that are missing or for links that go nowhere, where your HubSpot plan includes redirects.
On blog posts, edits to the post body: a missing or extra main heading, images with no text description (alt text), and unsafe resources on a secure connection.
For 16 more kinds of issue, Kennext writes the exact change and your team pastes it in. That includes robots.txt and sitemap settings, which HubSpot keeps in your account settings, and body edits on pages other than blog posts. Everything else Kennext finds, such as thin pages, weak internal links or missing pages, comes with plain-language guidance, because it needs content or hosting work rather than a setting.
Kennext connects with a HubSpot service key that has one scope, Content. It covers your pages, blog posts and redirects. With it, Kennext can:
Kennext checks the key's scope when you connect and tells you if Content is missing.
Sign in to Kennext (or create a free account) and scan your site.
In HubSpot, open Development, then Keys, then Service Keys. You need to be a super admin, or have developer tools access.
Create a key called Kennext with the Content scope, and copy it.
In Kennext, open Settings, then Integrations, then HubSpot, click Set up, paste the key and click Connect. If your HubSpot account serves more than one of the sites you scanned, Kennext asks which one to fix.
Open any issue on the board that shows Fix it for me. Review the before and after and approve.
Kennext scans your public pages the way a search engine does: titles, descriptions, headings, content, links, structured data and images. The HubSpot connection lets Kennext match each scanned page to its HubSpot page or blog post, including pages on your own domain, and read the current value of the field a fix would change.
On HubSpot, approving a fix publishes that one setting. Before writing, Kennext checks that the field still holds the value it read. If someone has changed it since, nothing is written and Kennext shows you the new value.
If you have an unpublished edit in HubSpot to the same setting, Kennext writes nothing until you tick Replace my unpublished edit to this setting. Your other unpublished edits stay as they are. Kennext never publishes them.
You can approve one fix at a time, or up to 20 fixes of the same kind at once with Approve all. A switch in Settings, Pause all fixes, stops any new approval until you turn it off.
Kennext rechecks each fix on your live site 1, 5 and 15 minutes after it goes live. When the check passes, the fix and its issue are marked Verified. If the check still fails after the last recheck, the fix is marked for review and the issue stays open, so nothing is marked done that is not.
Every change Kennext makes can be reverted from the same card. Revert writes the previous value back, and the issue goes back on the board. For Open Graph and structured data, revert removes Kennext's block and leaves the rest of your head code untouched.
In Kennext Settings, click Disconnect on the HubSpot card. Kennext forgets the key. HubSpot does not let an app delete a service key, so delete it yourself in HubSpot under Development, Keys, Service Keys. Fixes already applied stay on your site, and you can still see the history in Kennext.
Kennext stores the service key encrypted, never logs it, and never shows it to anyone. Settings shows its last four characters so you can tell which key is connected. Kennext keeps the previous value of each field it changed, so revert works, and a record of who approved what and when. Page data read for a fix is also sent to the AI services that write Kennext's suggested fixes. The Privacy Policy lists them and what they receive.
Email hello@kennext.ai. Include your site's address and, if it is about a specific fix, the card's reference (it starts with R-).
A service key with the Content scope. It covers your pages, blog posts and redirects. Kennext checks the scope when you connect.
No. Approving a fix publishes that one setting. If you have an unpublished edit to the same setting, Kennext asks before replacing it, and it never publishes your other edits.
No. Kennext writes a fix after you approve it, and you see the before and after before you approve. A Pause all fixes switch in Settings stops new approvals.
Kennext writes Open Graph tags and structured data as their own marked blocks and changes nothing else in your head code. Reverting removes the block.
Yes. Every change can be reverted from the same card in Kennext, which writes the previous value back.
Kennext forgets the key. Delete it in HubSpot under Development, Keys, Service Keys. Fixes already applied stay on your site.
Run a free scan and get a snapshot of what is holding your site back.
Get free scan