Keep your website current without learning a page builder.
Drop finished-job photos into a folder and a person puts the strongest ones on your site. Type any other change into one box and it reaches your TruLata team as a numbered ticket, logged, and a person makes the change.
Is my site live, and what is it running on?
Open the Website view and the first card is your live site. It carries a Live badge, a short list of facts about your build, and a button that opens your domain in a new tab. The facts are the ones a site owner asks about: the day it went live, how many pages it has, whether SSL is active, which forms it runs and how they are protected, whether Search Console is verified and the sitemap submitted. Beside it, a Recent website updates card lists dated changes to the site. The view appears in the Configure group of the sidebar only where a site has been set up for it.
Some rows are counted, not typed. Where your site publishes a sitemap, the page count is read off the sitemap each time the dashboard's data is pulled, and the blog count comes from the posts themselves, so a number that grows twice a week never goes stale on the card. Where the site is a storefront, the card reads the product count from the store and the last 30 days of sessions from Google Analytics 4. A row that cannot be counted is stated by our team when the site is set up.
The Live badge is a label, not a monitor. The card states what your site is built on; it does not check whether the site is up. The dashboard around it refreshes when you open it: last night's snapshot loads first, the live payload follows from a cache, and a pull runs behind the page when the snapshot is older than five minutes. A fallback snapshot is baked for every client at 12:01am Central, and a failed pull leaves the previous page up rather than an empty one.
How do I get new job photos onto my site?
Drop them into the folder on the card. The second card, Add photos to your site, links to a shared photo library, one folder per gallery or per service, and each link opens that folder in a new tab. Take the photos on your phone, drop them into the folder, and you are done. No page builder login, no resizing, no ticket to write.
A person looks at every batch. Your TruLata team reviews the photos, removes anything that shows a house number or a timestamp, and adds the strongest shots to the matching gallery. On a site we host as static files, the gallery change is a re-render and a redeploy; the photos do not touch the live site until that happens.
The review stays with a person on purpose. A folder holding every shot from a job is not a gallery, and a photo with the customer's address in the frame should not go up. The review is what makes the folder safe to use without thinking about it, and it is why the card is a folder rather than an upload button that publishes straight to the page.
How do I get something on my site changed?
Type it into the box. The Request a website change card asks for three things: which page, what should change, and your name. Text edits, photo swaps, new sections, seasonal updates, whatever it is, describe it in plain words and press Send to your TruLata team.
One send does four things. The request is written to a log with your name, the page, your words and the time. A ticket is opened against your account, and the screen shows you its number the moment it is sent, so you can quote it back to us. The Slack channel kept for your account on our side gets the request, and so does [email protected], so the whole team sees it. Each of those legs fails on its own if it fails, the others still run, and a request is never refused on a formatting rule.
A person makes the change. The request does not touch the site. It is one of the four write paths the screen has, all listed on the Security page, and none of the four writes to your site, your ad account, your CRM or your Business Profile directly. Simple changes typically go live within one business day. Our replies on the support thread are mirrored onto the ticket, and the Support tab lists every ticket with the date it opened, whether it came from the dashboard or from an email, its subject and its status: Open, Waiting on you, or Resolved. An email to [email protected] opens a ticket the same way.
Can I change the words on my site myself?
Yes, on a site we host as static files, and it happens somewhere else. The editor lives at its own address behind its own login, a one-time PIN sent to your work address, so you need no account and no password. One verified email maps to one site, so nobody opens another client's editor. It edits a set of labelled fields chosen for your site: headings, paragraphs, button text, contact lines and lists.
Press Save and three things happen in order. The fields are validated, the static site is re-rendered from its content file, and it is redeployed. Your public site stays 100 percent static: no editor script, no CMS, nothing extra for a visitor to download. The editor runs on two client sites today plus concept sites, and the Sites editor page describes it in full. Sites on WordPress keep their own editor.
There is no generator that turns a prompt into a site, and this page does not describe one. Layout, theme and the facts several pages depend on stay in the build, so an edit cannot make one page disagree with another.
Do the leads from my site show up on the dashboard?
Yes, and they arrive by the one road every lead has to travel. When someone submits a form on your site, the form handler appends the submission to a lead sheet on the server and emails your team. The Leads view reads that sheet, newest first. So the website and the Leads view are joined at the form, not at a tracking tag, and the sheet keeps filling on a day when every tag on the site is dead.
The status card says so in one row: every lead emailed and logged to a shared sheet. On a dashboard whose forms feed that sheet, a watch runs every morning at 7:20 Eastern and compares the sheet with what Google Ads and GA4 counted; the Leads page lays out its five checks. Nothing here reads your inbox or your calendar, and no call-tracking system exists: a phone lead counts only where your CRM records it.
What do I need to set up, and what should I check in the demo?
Nothing, if we built your site. The status card, the photo folders and the request box are set up for your site by our team during setup, which takes two to four weeks and is not billed. The photo library is a shared folder, and its link sits on the card. Where the site is on WordPress, the connection reads site status and publishes through its API, made from the inside with access you grant. There is no wizard and no sign-in button on our site, and we do not hold your passwords. The Website view is part of the Command Center, on all tiers, and support tickets are on all tiers.
Open demo.trulata.com and click Website. It is the same engine code every client runs, on a fictional company, with no form to fill and every number illustrative. Check four things. Read the status card and find the Open button. Open the photo card and count the folders, one per gallery. Type a request into the box and press Send: on the demo the message says the send is simulated and that on a live account it goes straight to your TruLata team. Then open Support and read the two sample tickets, one from an email and one from the dashboard, and click the resolved one to read the reply beneath it.
Then ask about what the demo cannot show. Ask for one real ticket, with its number, the Slack post and the support thread that answered it. Ask which of your status rows will be counted and which stated. Ask whether your site qualifies for the editor, which runs only on the static sites we host.
What the website view reads and writes.
| What | Where it comes from | How fresh |
|---|---|---|
| Site status card | Set for your site by our team; page and post counts read off the sitemap where it publishes one | At each pull, live on open |
| Photo folders | A shared photo library, one folder per gallery | Reviewed by a person, then published |
| Change requests | Logged, ticketed, posted to Slack and emailed to [email protected] | Live, ticket number on send |
| Support tickets | Every dashboard request and every email to [email protected] | Live, with our replies mirrored |
| Content editing | Separate editor, one-time PIN login, static sites we host | Per site |
| Direct edits to the site from this view | None | Never |
Every change to your live site is made by a person: photos after a review, requests after a ticket, and copy edits through a separate editor that re-renders and redeploys the site on save.
Questions, answered.
Is this a page builder?
No. It shows your site's status, takes photos into a shared folder for review, and sends change requests to your TruLata team as numbered tickets.
How do photos get onto my site?
Drop them into the folder for that gallery. A person reviews each batch, removes anything showing a house number or a timestamp, and puts the strongest shots on the site.
Can a change request break my site?
No. A request is logged and ticketed and goes to a person, who makes the change. Nothing on the view writes to the site.
How do I know my request was received?
The screen shows a ticket number the moment you send. The Support tab lists the ticket with its status, and our replies on the support thread appear beneath it.
Can I edit text myself?
Yes, on static sites we host, through a separate editor at its own address behind a one-time PIN login. A save validates the fields, re-renders the site and redeploys it. WordPress sites keep their own editor.
Does the view check whether my site is up?
No. The status card states what your site is built on, and the Live badge is a label, not a monitor. Page and post counts are read off the sitemap at each pull where your site publishes one.
Do site leads show up here?
On the Leads view. Your site's form handler writes each submission to a lead sheet on the server and emails your team, and the Leads view reads that sheet newest first.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.