Votel App Builder

Tutorial 3: Client portal

In one long session you'll have a portal where each client logs in, sees only their own websites, runs a speed and SEO health check, tracks scores on a chart and uploads brand files. You run it as the agency admin.

40+ min with approvals 7 numbered requirements 1 free Google API key
Built and tested in a live Votel account on November 21, 2026: real health checks ran with our own PageSpeed key, and a test PNG uploaded. Labels can change as Votel ships updates.
Before you start

What you'll build

You'll build a multi-page "Client Website Health Portal" for your agency, with two kinds of users and data kept separate per client company.

What you'll build

  • Email and password login with two roles: agency admin and client user
  • Admin pages for companies, websites and client users
  • A client dashboard with a Run health check button that stores performance, SEO, accessibility and best-practices scores
  • A score history chart, the top 5 fixes, and a brand assets page for uploads

What you need

  • A Votel account
  • A free Google PageSpeed Insights API key
  • An hour, with time to read approval cards
  • Tutorial 1 done first (recommended)
01

Get a Google PageSpeed API key

Get your own key before you start. Google's shared keyless quota ran out during our test, so every health check failed until a key was added.

In Google Cloud Console, go to APIs and Services, then Credentials, then Create credentials, then API key, for the PageSpeed Insights API. The free key allows 25,000 checks a day. Keep it somewhere safe. You'll paste it into a secure form in step 4.

02

Open Web Apps and paste the prompt

Click Websites, open Web Apps, click New web app, then paste this prompt and press Enter. Numbered requirements, then clear stop points.

Prompt · Client portal
Build a multi-page web app called 'Client Website Health Portal' for a marketing agency. Requirements: 1) Login with email + password and two roles: agency admin and client user. Each client company sees ONLY its own data (per-company isolation). 2) Admin pages: list client companies, add a company, add its websites, invite client users. 3) Client dashboard: their websites, each with a 'Run health check' button. A server function calls the Google PageSpeed Insights API for mobile, using my own API key (ask me for it in the secure key form, and confirm the deployed function sends it), and stores performance, SEO, accessibility and best-practices scores with a timestamp. 4) Website detail page with a line chart of score history and a table of the top 5 audit opportunities from the latest run. 5) Brand assets page where clients upload logos and images (PNG, JPG, SVG, PDF up to 10 MB), visible to their company and the agency only. 6) When a health check finishes, queue a short summary to the company's contact email. 7) Polished UI: sidebar navigation, purple accent, mobile friendly, empty and loading states. Build and test everything you can in the preview. Do NOT publish, do NOT send any email, and do NOT create users or records outside the preview without asking me first: stop and ask at each approval. At the end, list every requirement you could not meet and why.
What we changed after testing. Our first prompt asked for the keyless PageSpeed API and for emailing every client user. Neither worked (see Limits it hit), so this version asks for your own key and a queued summary to the company's contact email.
03

Approve the backend

This app needs logins, tables and file storage, so the assistant asks before it sets up the backend. Read the fee line, then approve.

The Votel assistant's plan for the client portal, a nine-item checklist starting with Set up backend, needs your approval, and a note that the backend starts a monthly fee of $0.00 a month
The plan and the first approval: the backend, at $0.00 a month in our test. Approving it also turns the chat into an App project.

In our run that one approval set up 5 tables and a file bucket. Then it built every page, checked its own screenshots and fixed its own bugs: a missing Tailwind plugin, a server function calling a route that didn't exist, and code written against the wrong column names.

Three of the assistant's own check screenshots: the Vite starter page, an unstyled sign-in page, and the finished Website Health Portal sign-in page
The assistant catching its own mistakes: starter page, unstyled page, then the finished sign-in screen.
04

Paste your PageSpeed key into the secure form

When the assistant needs your key, it shows an Add your API keys form in the chat. Paste the key there and click Save. The value is encrypted and goes straight to the app.

The Add your API keys form asking for PAGESPEED_API_KEY, with a note that Google's shared quota is used up and a free key allows 25,000 checks a day
The secure form for PAGESPEED_API_KEY. "Sent straight to your app, never to the chat."
Never paste a key into the chat. Only into the secure form.
Saved is not the same as used. In our run, checks still failed with "quota exceeded" after the key was saved. The assistant read its own function and found it never sent the key to Google, patched it, and found the fix hadn't deployed yet. A second redeploy fixed it. If checks still fail after you add a key, paste the follow-up below.
Fix prompt
Health checks still fail after I saved PAGESPEED_API_KEY. Check that the run-health-check function sends the key to Google, redeploy it, confirm the deployed version is the new one, then run one check and show me the scores.
05

Test it yourself

Test as the agency admin in the preview. Creating real client users is a separate approval, so leave it until you're ready.

CheckDo thisYou should see
Sign-in pageOpen the previewEmail and password fields, and a Forgot password link
Admin pagesAdd a company and one websiteBoth listed in the admin pages
Health checkClick Run health checkFour scores saved with a timestamp
Score historyOpen the website detail pageA line chart and the top 5 audit opportunities
UploadsUpload a PNG on the brand assets pageThe file listed, with download and delete
Gap reportRead the assistant's last messageEvery requirement it couldn't meet, and why
The Website Health Portal client dashboard for a test company: 1 website, 4 health checks run, 1 with errors, an Example.com card with Perf 100 and a Run health check button, and a list of recent health checks
The client dashboard after real health checks on a test website. The one Error came from a check before the key was wired in.
Screenshot coming soon

The website detail page: a line chart of score history and a table of the top 5 audit opportunities. The page was built and our test website had 3 runs, but we haven't pictured it yet.

Score history chart: screenshot coming soon.
Screenshot coming soon

The brand assets page with a file listed. A test PNG uploaded fine in our run, but we haven't pictured the page yet.

Brand assets upload: screenshot coming soon.
Learn from our run

Limits it hit

The portal mostly worked first time. Two requirements ran into platform limits, which is why the prompt now asks for a gap report.

RequirementWhat happenedWhat to do
Health checks with no keyGoogle's shared keyless quota was used up (HTTP 429)Use your own free PageSpeed key, 25,000 checks a day
Email every client user after a checkServer code can't list a company's usersQueue a summary to the company's contact email
Per-company isolation17 of 18 checks passed. The last needs real client usersTest with one real client user before you go live
Using the saved keyThe first deployed function never sent the key, so checks kept failingAsk it to confirm the deployed function uses the key, then run one check
When it passes every check

Publish, share and tweak

Publish once the health check, chart and uploads all work. Type "Publish this app." and read the card. Then connect your own domain so clients see your brand.

  • Connect this app to portal.mydomain.com.
  • Add my agency logo to the sidebar and the sign-in page.
  • Add a desktop score next to the mobile score on each health check.
If something looks off

Troubleshooting

Bigger apps hit more snags. These are the ones we saw.

You seeWhyFix
Health check fails with "quota exceeded"No API key, shared quota used upPaste your PageSpeed key into the secure form
Still "quota exceeded" after adding the keyThe deployed function doesn't send the key yetUse the fix prompt in step 4
An approval card to delete a function or table you didn't ask aboutThe assistant listed it as test cleanup by mistakeDeny it and ask why. Only approve deletes of test records
Unstyled pagesA missing Tailwind pluginAsk: "The page is unstyled, fix the Tailwind setup"
A button does nothingA server function calling a route that doesn't existDescribe the button and what you expected
Blank preview or console errorsThe preview server went to sleepAsk: "Restart the preview"
Quick answers

FAQ

Can each client only see their own data in a Votel app?

Yes. Votel apps support roles and per-company data isolation. In our portal test the assistant verified 17 of 18 isolation checks. The last one needs real client users, which we didn't create.

Why do I need my own PageSpeed API key?

Without a key, the app uses Google's shared keyless quota, which ran out during our test (HTTP 429, quota exceeded). Your own free key from Google allows 25,000 checks a day.

Can the portal email clients after each health check?

Not to every client user. Server code can't list a company's users, so the assistant queued a summary to the company's contact email instead. App email only goes to the app's own users, 200 recipients max, and needs approval.

What file types can clients upload?

Our prompt allowed PNG, JPG, SVG and PDF up to 10 MB. Votel apps take files up to 25 MB by default and 100 MB at most.

Your turn

Try it in Votel

New to the builder? Do the ROI calculator first. It takes 15 minutes and teaches you the whole flow. Votel has a 14-day trial, then plans are $97 or $297 a month.

All Things Votel is an independent site, not operated by or affiliated with Votel.ai. Links to Votel are affiliate links. Built in a live account on November 21, 2026. Labels may change.