Viewfield + GitHub
Connect the repository your site is built from and Viewfield can read its page files and open a change from AI visibility as a draft pull request your team reviews and merges.
- Pages as Markdown, MDX or HTML files, mapped from URLs by rules you set
- A change is one commit on its own branch and a draft pull request
- Merging is yours: Viewfield never merges
- The files your URL rules name, on the branch your site deploys from
- A branch, one commit and a draft pull request, when a person decides a change
What GitHub does in the loop, as your website.
Your own pages
Viewfield connects only a site served on your own hosts, and reads the pages AI answers cite or should.
A draft, on a decision
A change proposed from AI visibility shows every field before and after. Saving it writes the CMS's own draft, a revision or a pull request; nothing goes live on its own.
Publish is yours
Publishing is a separate press, offered only where the CMS has a draft to promote. A page someone edited since the proposal is never overwritten.
Never merges or pushes to your site's branch
Never reads a repository other than the one you name
Never touches a site that is not on your own hosts
Every action here is also an MCP tool, so Claude, Cursor or any MCP client can drive GitHub through the same doors your team uses, with the same QA. npx @viewfieldai/mcp install
Connect GitHub in minutes.
Included on every plan. Every plan starts with a 14 day free trial. No credit card to sign up.