WordPress updates by email.

Update your existing WordPress site by email. You have a website. You want a change. You don't want to log in, hunt for the right page, fight the editor, or wait until business hours to reach your webmaster. You email wordpress@forco.ai with what you need. The Forco AI WordPress assistant replies with a plain-English preview of the change. You approve. It ships. You go back to your life.

Send it by email or by Telegram voice note

Two ways in, same skill behind both. Whichever is closer to hand:

• Email wordpress@forco.ai. Plain English. Attach files if you have them. Reply to the preview to approve or correct it.
• Telegram on the run. Type it, or record a voice note. Forco transcribes the voice note, drafts the change, and sends you the preview to approve from your phone. Made for the cab, the kitchen, the walk home.

Same job, same approval step, same audit trail. Use one or both. We don't make you choose.

Why people use it

• You already have a site and you want updates. Not a rebuild. Not a new theme. Just keep it current.
• Save money. No agency retainer for ten-minute jobs. No four-hour minimums to fix a typo.
• Get it done when you want it done. Friday evening. Public holiday. The middle of the night when an idea wakes you up. Forco is awake too.
• Precision. Forco shows you the exact change before it touches the site. What page, what field, what before and after. You see it, then approve it.
• No editor to learn. If you can write the change in an email or say it out loud, you can ship it.
• Audit trail. Every change is logged with a screenshot and the live URL. Hand it to your accountant, your board, or your future self.

Use cases. What people are asking for.

A short and very incomplete list. The skill is general. If you can describe the change in a sentence or two, you can ask for it.

• Fix things fast. A typo on the pricing page. A broken phone number in the footer. The wrong opening hours on the contact page. The old founder photo on the about page.
• Publish content. A new blog post from a draft you wrote in Google Docs. A new landing page for a campaign you are launching tomorrow. A case study from a transcript.
• Swap images and media. Replace the homepage hero. Update the team photo. Drop a new product shot into a gallery. Update alt text across a page for accessibility.
• SEO touch-ups. Tighten a meta description that isn't pulling clicks. Add canonical tags to duplicate posts. Update internal links after a URL change.
• Bigger jobs. A whole new section on the services page. A pricing table rebuild. A FAQ block with ten questions. A new contact form that posts to your CRM.
• Time-sensitive changes. Push a sale banner up for the weekend. Take it down on Monday morning. Update the roster on the team page when someone joins or leaves.
• Compliance and policy edits. Refresh the privacy page after a vendor change. Add a cookie banner. Patch the terms to reflect a new product.

We don't put a ceiling on what you can ask for. Small fixes and large rebuilds both fit. If something is too risky for the skill to do without a developer, Forco will say so in the preview before anything happens.

How it works

1. First message: you agree to the terms. One click, once. Nothing is touched on your site before that.
2. First message: Forco asks for the access it needs. A username plus a WordPress application password (a revocable key you generate in wp-admin, not your main login). Stored safely and used only for the changes you ask for.
3. From then on, just send the change. Plain English. Email or Telegram. Attachments and voice notes welcome.
4. Forco replies with a plan. Which page, which field, the before-and-after, any risks it sees.
5. You approve in one click. Or reply with corrections and Forco redrafts.
6. Forco makes the change. If you have a staging site, the edit lands there first. Reply "push it live" and Forco promotes it. No staging? The change goes to the live site as a draft for you to publish, or live straight away if you've told Forco that's the workflow you want. Either way you get a screenshot and the live URL when it's done.

Working with a webmaster

You don't need a webmaster to use this. But if you have one, Forco fits next to them, not in their place.

• They can set it up on your behalf. Hand over the application password, plug it into Forco, hand the email address back to you. You email wordpress@forco.ai from there on. They never have to be in the loop for routine changes.
• They can pre-program how it behaves. Say you want every new blog post to land as a draft for you to publish, never live straight away. Or you want sale banners to auto-expire after the date in the email. Or new pages should always be added to the main menu in a certain place. Your webmaster sets that up once with Forco. From then on the skill follows the rules you both agreed.
• They can sit in front of the skill. Route every request through themselves first, decide which jobs Forco picks up and which they handle by hand. Useful when a site has unusual quirks the skill shouldn't guess at.
• They can sit behind the skill. Forco does the routine work, your webmaster gets a heads-up on anything that touches code or infrastructure.

Webmasters who refer clients to Forco can earn commission on the spend their clients put through the platform. See the partner program for the details.

What it won't do without a clear signal from you

• It will not run plugin updates or theme swaps that could break your site without a clear "I understand this is risky" from you.
• It will not touch the WordPress core, database, or wp-config.php. That belongs to a developer, not a content assistant.
• It will not publish anything before you approve. Auto-approve can be turned on later for narrow templates (for example, "publish a blog post when I email it from this address") but it's off by default.

What you'll need to connect

A WordPress site (self-hosted or WordPress.com Business and above) and a WordPress application password with edit-content permission. We walk you through it in a single email at signup. Multisite, Elementor, and Gutenberg are all supported.

Privacy

Forco only sees the change requests you send to wordpress@forco.ai (or to the Telegram bot) and the WordPress pages it has to edit to fulfil them. It does not crawl your site or read other content. Full details on the privacy page.

Launching soon

We're rolling this skill out to early-access members first. Join the waitlist to be among the first to use it.

Join the waitlist →