We answer. Actually.
SEO Merlin is built by a small team. When you write in, a human who works on the plugin reads it, not a ticket router, not a chatbot pretending to be one.
Email us
The fastest way to reach a person. Include your site URL and what you were doing when things went sideways.
support@seomerlin.comRead the docs
Setup, API keys, connecting Search Console, rolling back a scan. Most answers already live there, and it’s faster than waiting on us.
Documentation →Found a bug?
Tell us what broke and how to reproduce it. Bug reports jump the queue, they make the plugin better for everyone using it.
Report a bug →Five lines that get you a fix instead of a reply asking for more
Most support threads take three rounds because the first message is missing something. Paste these and we can usually answer properly the first time.
- Your site URL — and whether it’s live, staging or local
- What you were doing — the screen and the button, not just “it broke”
- What you expected vs what happened
- The exact error text — a screenshot of the message, or the response body from your browser’s Network tab
- Your setup — WordPress and PHP version, which SEO plugin you run, and whether an AI key is connected
Where to find the error text
If a scan or fix fails, the useful detail is usually in one of two places:
- Browser DevTools → Network, click the failed request, copy the Response tab
- Your host’s PHP error log — usually in hPanel or cPanel under Logs
A generic browser error page rarely tells us anything. The response body almost always does.
What to expect, honestly
We’d rather under-promise. These are typical, not guaranteed, and a clear bug report is usually faster than any tier.
Free
Answered, just not first. Usually within a few business days.
Pro
Email support, typically within one to two business days.
Freelancer
Priority queue. Usually same or next business day.
Agency
Priority queue, and we’ll take a call if a site is actually down.
Reproducible bug reports jump every queue, on every plan.
Things people write in about most
Check the Issues screen first: a refused write usually means the preview token expired, which happens after fifteen minutes. Re-run the preview and approve again. If it fails a second time, send us the response body from the Network tab, that carries the actual reason.
Open the fix history and undo it there, individually or in bulk. If undo reports drift, it means you edited that page after the fix: it stops rather than overwriting your later work, which is deliberate. You can still revert manually from WordPress revisions.
The two usual causes are no credit on the Anthropic account, or a key pasted with a trailing space. The plugin tests the key on save and reports back: if the test itself errors, send us that message.
Sign-in runs through our OAuth broker. If it fails, confirm you’re signing in with the Google account that actually owns the Search Console property: being an editor on the site isn’t enough. Access tokens also expire during our verification period, so a reconnect every few days is expected for now.
We don’t ask for admin access as a first step and you shouldn’t hand it out casually. Almost everything is diagnosable from the error text and your setup details. If a case genuinely needs it, we’ll say so and you can create a temporary account you delete afterwards.
Still stuck? Write in.
Include the five lines above and you’ll usually get a real answer rather than a request for more information.
Built by Devebo, a trading name of CARPEBO SINGLE MEMBER P.C. · WordPress 6.5+ · PHP 8.1+