Recover leads the contact form received but never emailed
Pulls every contact form submission, separates the leads whose email failed, builds a call list with spam filtered out, dates when failures started and proposes a relay fix for your approval.
When to use it
When you suspect your contact form emails stopped arriving and you may have lost leads without knowing it.
What you get
A call list of the real leads whose email failed (spam removed), the date the failures started, the likely cause, and a mail relay fix applied after your approval.
Does it change anything in my account?
Only with your approval. The assistant first shows a preview of every change and waits for your go-ahead.
Fill in before sending
[30]
I suspect we have been losing leads because form emails were not delivered. List my servers (ask me which one if there are several), then pull every contact form submission from my hosted site for the last [30] days. Use a high limit, and tell me if the result looks capped so we can narrow the window.
1. Split them into two groups: delivered, and failed or not sent (delivered:false).
2. For the failed group, build a table: date and time, name, phone, email, service requested, a one-line summary of the message, and the stored error text. Use whatever fields the form actually sends and mark missing ones as empty. Sort newest first and mark anything under 48 hours old as "call today". If tracking fields such as gclid or utm_source came through, add a column showing the source.
3. Move likely spam to a separate list: no phone and no email, links in the message, or text unrelated to our services.
4. Using the timestamps on the rows, count failures per day and tell me when they started and whether every submission failed after that date or only some.
Finish with: total real leads lost, the most likely cause based on the stored error texts (for example an expired or revoked app password, a sending quota, a temporary refusal), and the fix you recommend. Group identical errors together. If the error field is empty or vague, say clearly that the cause is an inference from the failure pattern, not a confirmed diagnosis. If the fix is a new app password or corrected mail settings, show me the exact configuration you would apply and wait for my approval. After I approve, apply it with send_test turned on and report whether the test email went out.
Finds page-one pages that get impressions but few clicks, compares them to your site-wide CTR, and rewrites their meta title and description around the queries that actually bring them traffic.
When to use itWhen your pages rank on page one and get impressions but few clicks, so your titles and descriptions are probably not convincing.
Matches GA4 landing-page performance against your WordPress menus, flags valuable pages missing from the navbar, dead weight and broken links, and proposes a leaner main menu.
When to use itWhen your site menu feels cluttered or outdated and you suspect it does not point visitors to the pages that actually bring conversions.
A plugin-by-plugin action list that flags outdated, duplicate and conflicting plugins and double-firing tags.
When to use itWhen your WordPress site has too many plugins, updates piling up, or you fear duplicate tags are inflating the conversions your ads optimize toward.