What a Client Portal Should Show a Business Owner

A business owner should be able to see the work on the website, the written record of each request and edit, and the posts waiting for a decision, without learning a page builder. On our Forged accounts, that view is the client portal. It is part of every account, the work is visible there, and the record of changes lives in writing [1]. Posts are approved by email or in the blog editor before they go live, unless you turn auto-publishing on [2].

What the account portal is for

Our view is plain. A site built for one business should carry only what that business needs. The account portal should show the record, the posts, and the publishing control, without a plugin stack to learn. The Forged Sites page describes that setup: the portal is where you publish the content that should stay in your hands, and where the record of changes lives in writing [1].

Three jobs belong in that view. The audit trail holds the asks, the edits, and who dispatched them [3]. The blog editor is where you review, edit, and approve posts, and where you can write a post or reshape one from your own jobs, photos, and notes [4]. The publishing control the page actually shows is auto-publishing: approval by email or in the blog editor comes before a post goes live, unless you turn that switch on [2]. There is no frequency slider on the page, and we will not describe a dial the page does not have.

If you need to edit every page yourself, a conventional content management system such as WordPress is the better fit. We still build those [7]. Forged fits an owner who wants publishing control without an open page builder on the core pages.

The record of asks and edits

A service line needs a clearer sentence. A phone extension changed. A photo from a finished job should replace an older one. Each of those starts as an ask, and the edit plus the person who dispatched it should stay attached to that ask [3]. If the sentence looks wrong later, the trail is a receipt, not a debate about a phone call.

A 2005 National Archives guide for federal agency staff says changes to a page's content that leave the page in the same place can be treated as a version-control issue, and that the agency has to decide how to keep track of those versions [8]. A private company is not that agency. The guide is not a statute for your business, and it is not legal advice. The narrow lesson is the one we build for: when a public page changes, someone should be able to see what was asked, what was edited, and who dispatched it.

We work from Charlotte. The portal is how an owner who is not in the room reads the same written record we use, so a small wording request is not later mistaken for a rebuilt page.

Posts you can review, edit, and approve

A post can arrive as a draft about your field. You read it, change a sentence that does not sound like the shop, and add a detail from a job only you were on. Then you approve it, in the editor or by email, before it goes live, unless you have turned auto-publishing on [2] [4]. A job photo plus a few notes will carry more of your voice than a draft built only from general research. The page says you can write a post, or reshape one, from your own jobs, photos, and notes [4].

The Google Search Central page on helpful, people-first content, updated on 2026-10-05, says people-first content is created primarily for people, not to manipulate search rankings [9]. The same page says it helps when it is clear who created the content, and it treats a large amount of generative text produced without manual oversight or curation as little to no effort [10]. We do not read that page as a ranking promise. We read it as a reason you should see the post, change it, and put a name to it before it is public.

With auto-publishing off, the draft waits. With the switch on, the approval step is no longer required before publishing [2]. The switch does not create a new volume control. The count of posts still follows the plan, and that pace is an allowance, not a promise of a particular search ranking or a set number of leads [5] [6]. If a draft is thin, or the topic is wrong, send it back.

The publishing control on the page

Some owners expect a slider for how often the site speaks. That control is not on the Forged page. What you have is the approval path and the auto-publishing switch [2]. Leave the switch off when you want the last look, which is the right setting if tone matters or the work is technical. Turn it on when you would rather the plan's pace continue without a separate yes on each item. Either way, volume runs from one post each month on Lite up to a daily pace on Ultimate [5].

Email and the blog editor are the two approval doors the page names [2]. A short correction can go back by email. A rewrite that needs the job photo in front of you belongs in the editor. Both ask the same question: is this post ready?

Why core pages stay reviewed

Home, services, about, contact, and the other core pages stay in the managed site. You ask for the change. You do not open those pages in a live page builder and publish them yourself. The Forged page says those pages, given a live editor, are how a site goes wrong in an afternoon: one skipped heading, one missed contrast choice, one dropped form label [11]. Core pages stay reviewed for that reason. Posts and portfolio items sit in a structured format, so a post or a job write-up is not an open rebuild of the homepage [12].

The W3C understanding page for Success Criterion 1.3.1 says information, structure, and relationships conveyed through presentation have to be programmatically determinable or available in text, and it points to headings, often set in a larger, bold font, as one of those visual cues [13]. A line that only looks like a heading, or a skipped heading, can leave that relationship behind. The eye still sees a section. The structure of the page may not.

The W3C understanding page for Success Criterion 1.4.3 says text and images of text need a contrast ratio of at least 4.5:1, large-scale text needs at least 3:1, and incidental text plus text in a logo or brand name has no contrast requirement [14]. Those ratios are thresholds, so a gray that looks fine on a laptop is not a casual choice [14].

The W3C understanding page for Success Criterion 4.1.2 says the name and role of a user interface component, including a form element, must be programmatically determinable, and it lists a control with no programmatically determined name as a failure [15]. A dropped form label is that failure in ordinary clothes. The box is still on the page. The name the control needs may not be.

None of those pages says a statute applies to you. We are not giving legal advice, and we do not promise ADA or WCAG compliance. They name concrete ways a core page fails when someone edits it in a hurry. That is why those pages stay reviewed, while open editing in the portal is aimed at posts and at the record.

When WordPress is the better fit

Some owners want to change every page themselves, on the evening they think of the change. For that owner, WordPress is the better purchase, and we still build those sites [7]. Forged is a poor fit if what you want is an open page builder.

The WordPress.org documentation page on managing plugins, last updated on 2026-01-10, says WordPress plugins are PHP scripts that extend the functionality of WordPress, and that you should keep your plugins up to date [16]. Plugins can add features the core software does not ship. They also become a list someone has to watch. That upkeep is a fair reason to choose WordPress when you want hands-on control of every page.

A stylesheet can grow the same way. The web.dev lesson on CSS nesting, updated on 2025-08-21, says nesting style rules can make a stylesheet more organized, easier to read, and more maintainable, and that nesting more than two to three layers deep can make maintenance more difficult [17]. We use that as a comparison, not as a buying rule. A plugin stack and a deep style sheet are both things a person has to maintain. The account portal is the smaller surface: the record, the posts, and the publishing switch. If you still want the keys to every page, take the CMS. We will build it.

Portfolio notes and the ads add-on

Portfolio photos and job write-ups are a short third path. They go on the site once you ask your account manager [18]. You send the photo and the write-up. You do not need a page-builder session to place them.

Paid ads are not inside the plan. They are an add-on at $149.99 each month, month to month, with no term [19]. If you have that add-on, the portal is where the ad record shows up. The page says the portal puts Google beside Bing and ChatGPT, with spend, leads, and cost per lead, refreshed daily [20]. You see the three platforms together. Seeing those figures side by side is not a promise that one platform wins.

The same page says neither a plan nor an add-on promises rankings, a lead count, or any return on ad spend, and social media management is not included [21]. Those figures are a record, not a forecast and not a promise that leads will arrive. You pay the ad spend straight to each platform. The accounts are opened in your name, and they stay yours [22]. If the add-on is off, that ads view is not part of the portal.

Practical takeaways

• Use the account portal for the written trail: the ask, the edit, and who dispatched it [3].
• Review, edit, and approve posts in the blog editor or by email, and turn auto-publishing on only when you want that control. Volume follows the plan, from one post each month on Lite up to a daily pace on Ultimate [2] [5].
• Keep core pages out of a live page builder. A skipped heading, a weak contrast choice, or a control with no name is a real miss, and if you need to edit every page yourself, WordPress is the better fit. We still build those [7] [11].

How we can help

Have more questions or want to get in touch? Visit the contact page, call (980) 322-4500, or email [email protected].

Citations

1. Idea Forge Studios, "Forged Sites" (2026)
2. Idea Forge Studios, "Forged Sites" (2026)
3. Idea Forge Studios, "Forged Sites" (2026)
4. Idea Forge Studios, "Forged Sites" (2026)
5. Idea Forge Studios, "Forged Sites" (2026)
6. Idea Forge Studios, "Forged Sites" (2026)
7. Idea Forge Studios, "Forged Sites" (2026)
8. National Archives, "NARA Guidance on Managing Web Records" (2005)
9. Google Search Central, "Creating helpful, reliable, people-first content" (2026-10-05)
10. Google Search Central, "Creating helpful, reliable, people-first content" (2026-10-05)
11. Idea Forge Studios, "Forged Sites" (2026)
12. Idea Forge Studios, "Forged Sites" (2026)
13. W3C, "Understanding Success Criterion 1.3.1: Info and Relationships" (2026)
14. W3C, "Understanding Success Criterion 1.4.3: Contrast (Minimum)" (2026)
15. W3C, "Understanding Success Criterion 4.1.2: Name, Role, Value" (2026)
16. WordPress.org, "Manage Plugins" (2026-01-10)
17. web.dev, "Nesting" (2025-08-21)
18. Idea Forge Studios, "Forged Sites" (2026)
19. Idea Forge Studios, "Forged Sites" (2026)
20. Idea Forge Studios, "Forged Sites" (2026)
21. Idea Forge Studios, "Forged Sites" (2026)
22. Idea Forge Studios, "Forged Sites" (2026)