Connect Facebook Page to SiteOps
A large share of the internet still spends its day on Facebook, and a brand Page there costs nothing to run. Posts on a Page reach your followers, get shared onward, and give your brand a public home that search engines and people can both find.
The one rule that shapes this whole setup: outside tools can only post to a Facebook Page, never to a personal profile. That is Meta's rule, not ours, and it is a good one — it keeps automated posting on business surfaces and out of people's personal feeds. So the first question is not about SiteOps at all: does your brand have a Page, and are you one of the people who manage it?
Once connected, SiteOps publishes the posts you approve to the Page and reads back how many people each one reached. If you already connected Instagram, this will feel familiar — it is the same Meta plumbing, the same consent screen, the same Facebook login. A connected Page also quietly sets you up for two neighbours: Instagram publishing (which requires a linked Page) and Meta Ads (which advertises from one).
One honest note about timing: Page publishing runs through SiteOps's own Meta app, which Meta reviews once for the whole platform (the permissions to post and read Page engagement). That review is a one-time SiteOps step, not something you do — but on a freshly reviewed app, Page publishing may take a little while to become available while Meta finishes granting it. Your sign-in and role setup are still worth doing now.
Set it up, step by step
0 of 8 done
- facebook.com
- Pages
- Create new Page
- Page settings
- Page setup
- Page access
- business.facebook.com
- Business settings
- Accounts
- Pages
- Settings
- Facebook Page
- Connect
What lands on the Page — short on purpose, media optional Check the Page itself, logged out or in a private window, to see the post the way the public does.
Let an agent do it
An agent with access to your browser can run the pre-flight checks for you — confirm the Page exists, verify your role on it, and check the Business portfolio linkage — so the only click left is the Meta consent screen.
Check that my Facebook Page is ready to connect to SiteOps.
1. Open https://www.facebook.com/pages/?category=your_pages and confirm a Page named <my brand's Page name> is listed. If it is missing, tell me — do not create one without asking.
2. Open that Page's settings and find Page access (new Pages) or Page roles (classic Pages). Confirm my login has full control / admin. Report the exact role you see.
3. Open https://business.facebook.com/settings/pages and check whether the Page is held as an asset in a Business portfolio. If it is, confirm my login has access to it with permission to publish content.
4. Report back a short checklist: Page exists (yes/no), my role, portfolio linkage, and anything that would block an outside tool from publishing.
Do not change any roles, settings or permissions — read and report only.The Meta consent screen is yours alone: you press Connect in SiteOps, sign in, and approve the permissions yourself — an agent should never click through an OAuth consent for you. Creating a Facebook account or a new Page is also a human job.
If something does not work
- My Page does not show up when I connect
- Your role on the Page is the usual cause — you need full control (admin), not a partial role like content-only. If the Page lives in a Business portfolio, also check at business.facebook.com under Business settings, then Pages, that your login has access to the Page as an asset. Then disconnect in SiteOps and connect again so Meta re-reads the list.
- The connection is green but nothing publishes
- A permission was declined on the Meta consent screen — usually the one about publishing content. Disconnect Facebook in SiteOps settings, press Connect again, and leave every permission switched on this time.
- Can SiteOps post to my personal profile instead?
- No — and no tool can. Meta only allows outside tools to publish to Pages. If your brand currently lives on a profile, create a Page at facebook.com/pages/create and post there; Facebook also offers a migration path from profile to Page.
- The connection shows Needs attention after working fine
- Something changed on the Meta side — a password change, a role removed, or the Page moved in or out of a Business portfolio all expire the access. Check that your login still has full control of the Page, then reconnect in SiteOps.
- Posts publish but the Social card stays empty
- Fresh insights can lag a few hours on Meta's side, so give a new post until the next day. If the card stays empty after that, the insights permission was likely declined during consent — reconnect and grant everything.