Set up contact form email delivery on my hosted site with my own Gmail
Checks the contact form on your hosted site, connects your own Gmail or Yandex as the sender after you approve the setup, sends a test email and confirms the lead is recorded.
When to use it
When your hosted site's contact form needs to send new leads to your own Gmail or Yandex mailbox and you want to be sure it works.
What you get
A working contact form that emails each lead to your Gmail or Yandex address, confirmed by a test email and a form submission that shows up as delivered.
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
[Gmail or Yandex address][website name]
Our website runs on the Opus Growth hosting server. The contact form must email every new lead to [Gmail or Yandex address].
1. List my servers. If there is more than one, ask me which one hosts this site. Then show the site's address and status.
2. List the site files, find the contact page and read it. Tell me which form exists and which fields it actually sends (name, phone, email, service, message). Flag any field from that list that is missing, and note whether the form already posts to the Opus Growth relay.
3. Tell me exactly what you need from me to connect my own mailbox and why. For Gmail that is a Google app password, not my normal password. For Yandex, also tell me whether an app password is needed.
4. Before applying anything, show me the configuration you plan to set: provider, sending account (from_email), recipient (to_email) and one fixed subject line, for example "New lead from [website name]". The relay uses a single static subject and has no reply-to setting. The visitor's name, email and other fields will appear in the email body, so I will reply by copying their address from there.
5. Apply the configuration only after I confirm, with send_test turned on so a test email goes out right away. Tell me whether the test was sent or the error it returned.
6. Read the live contact page and confirm the form posts to the relay. If the form needs an edit (wrong action, a missing phone field, field names that will not come through), show me the exact before and after code and wait for my approval before editing the file.
7. Ask me to submit one test entry on the live form. Then pull the form submissions from the last day and confirm my entry is there with every field filled, and whether it was delivered or failed with an error.
If anything blocks delivery, such as a wrong recipient, an authentication error or a missing field, list it with the fix you propose, and wait for my approval before changing anything.
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.