Your schedule, documents and files already live in Google. Your public site lives in WordPress. WPOS sits between the two and moves work across on request — reading a calendar, a doc or a sheet and turning it into native, editable WordPress. No plugin installed, nothing syncing behind your back.
Most businesses already own the content their site is missing — it just lives in Google. The events are in a calendar, the approved copy is in a Doc, the price list is in a Sheet. Getting any of it onto the site means someone retyping it, quietly losing half the formatting, and then doing it all again next month when the source changes.
The usual shortcut — a Google iframe — gives you an embed you can’t restyle and can’t get indexed. WPOS closes that gap without a plugin: it reads your Google content and rebuilds it as real WordPress you own.
A one-time connect from Settings and then Connectors. Bring your own Google account; Calendar, Docs, Sheets and Drive are supported. Nothing is installed on the WordPress side, and connector status is checked at the start of every conversation — so the fastest way to confirm what’s live is simply to ask.
Pull the next six events onto the homepage. Build the About page from this doc. Turn the price sheet into a styled table. You name the Google source and the page; WPOS reads the range or document, normalises the fields, and decides what’s actually publishable — attendee emails, reviewer comments and internal notes stay out.
The content becomes a themed widget, page content, custom fields and SEO metadata — styled with your existing design tokens, not dropped in as a foreign embed. Images and PDFs from Drive are rehosted in your media library, never hot-linked. The page is loaded in a real browser and screenshotted before it’s called done.
A pull can be set to repeat — every morning, every Monday, before every publishing run. That’s how an events section or a policy page stays accurate without anyone remembering to update it. The site holds a snapshot, refreshed when you ask; it is not a live feed.
Four Google Workspace apps are supported today: Calendar, Docs, Sheets and Drive.
Your calendar answers the question visitors ask most — what’s happening and when — and almost no one sees it. WPOS reads it and builds real, indexable content, and it works both ways: events can be written back into the calendar from a conversation.
Pull the next six events onto the homepage as a native section rather than an embedded iframe. Give each event one permanent URL with Event schema so results can show the date and venue. Build a weekly class grid the front desk still edits in Calendar, or a closure notice that removes itself once the window passes.
Almost every page was written in a Doc first. WPOS reads the document as structure — headings become sections, lists stay lists, tables and links survive — and rebuilds it in your theme, rather than pasting a wall of styled text.
Turn a signed-off copy deck into a live page with the approved wording word for word, laid out as real sections. Keep policy, legal and price pages authoritative in the Doc, then refresh the page from it and see what changed. Turn a support-answers doc into an FAQ with schema, or export a page’s copy into a Doc for a client to comment on and apply what they approve.
A spreadsheet is the one editor most non-technical clients actually prefer. WPOS reads a range and builds a styled, responsive table themed to your site — and can write to the sheet too, so a form’s enquiries or a launch checklist land as rows.
Keep services, prices or hours in a sheet, one row per item, and rebuild the widget when it changes. Turn a price list or comparison range into a native table widget instead of a raw Google frame. Maintain a product catalogue in a sheet and create or update WooCommerce products in bulk, far faster than the WordPress admin.
Bring your own Google account. Connect it once from Settings and then Connectors — Calendar, Docs, Sheets and Drive are supported (among WPOS’s 18 connectors, not a directory of thousands). Everything WPOS builds is native WordPress, fully editable, no lock-in: no plugin is installed and no third-party iframe is left behind. It’s a snapshot taken when you ask or on a schedule you set — not a live sync, and nothing publishes on its own.
What connects, what it builds, and why it’s a snapshot rather than a live feed.
Connect your Google account once from Settings and then Connectors in WPOS — a single authorisation, no plugin installed on the WordPress side. Calendar, Docs, Sheets and Drive are supported. After that you just describe what you want in plain language, such as pull the next six events onto the homepage, and WPOS reads the source and builds it as native WordPress. Status is re-checked at the start of every conversation, so you can always ask what’s currently connected.
Yes. Name the sheet and the range, and WPOS reads it and generates a styled, responsive table widget themed to match your site — not a raw Google embed. It’s a publish step, not a live link: re-run the pull, or put it on a schedule, when the sheet changes and the table updates. Sheets can also drive service lists, price blocks and bulk WooCommerce product loads.
Point WPOS at the document and say build it as a page. It reads the doc’s heading hierarchy and maps H1, H2 and H3 to your page outline, keeps lists, tables, bold and links intact, and uploads any images into your media library. The result is a designed, editable page — not a flattened paste. Accept any tracked suggestions first: a doc in review mode reads as its accepted text, so resolve the review before pulling.
Yes, without an iframe. WPOS reads the events out of your Google Calendar and builds a native, indexable section — an upcoming-events list, a full page per event with Event schema, a weekly timetable, or a countdown to the next launch. Recurring events are expanded into their real dated instances, and private detail like attendee emails is kept off the public page. Pair it with a scheduled refresh and the section maintains itself.
A snapshot. There’s no webhook and no always-on listener — changes in Google reach the site on the next run, on request or on a schedule you set. If an event moves in Calendar at noon and the refresh runs at midnight, the page shows the old time until then. Plan the refresh interval around how fast your content actually changes; for volatile content, refresh more often.
Not for this page yet — the Google Workspace integration is documented here from the capability reports while its demo is produced. Every capability described is real and supported today. The quickest way to see it is to connect your own account and try the first move: name a calendar, doc or sheet and a page, and WPOS builds and screenshots the result in a single request.
Start free with 10,000 credits, one live site and a sandbox, no card required. Bring your own Google account and turn your calendar, docs and sheets into native WordPress. Running an agency? Book a call.
Start free