A workspace you can arrange
Move and resize windows, switch through the taskbar, and use the desktop’s layout controls. Keep a report beside a task or a website control beside reference material.
THE WORKSPACE BEHIND THE WEBSITE
Your website.
Your work.
In view.
Build the website. Understand the visitor. Plan what happens next.
PC NET DESK brings connected analytics, competitor intelligence, website creation, and scheduled changes into a familiar desktop. See the journey from first visit to inquiry, then use Core Console, the Style Engine, and the Website Builder Engine to improve it.
Four connected tools. 100 capabilities. 18 interface screenshots.
PC NET DESK01 / THE WORKSPACE
View the actual interface A familiar starting point.
Apps, windows, and website controls, brought together.
THE BIG PICTURE
One system.
Four distinct jobs.
The tools overlap by design. They let you move from understanding a problem to making a change, without rebuilding your working context.
01 / WORKSPACE
PC NET DESK
The desktop that brings the tools together.
Open apps. Arrange windows. Keep related work in view.
Explore Desk 02 / UNDERSTANDINGCore Console
The organized dashboard behind the workspace.
Review activity, manage records, and use direct commands.
Explore Console 03 / APPEARANCEWebsite Style Engine
A coordinated design system with visible controls.
Choose the website. Adjust its look. Preview the result.
Explore the engine 04 / CREATIONWebsite Builder Engine
The system for content, structure, design, and published pages.
Compose a draft. Refine the page. Publish a named snapshot.
Explore the builder Desk and Console are two ways into the management tools. The Style Engine changes presentation. The Builder changes the content and structure of a page. A command line inside Core Console provides a text-based route to supported operations.
Connected reporting shows what is happening. The Builder and Style Engine provide the controls to improve it. Tasks, approvals, notes, and scheduled settings keep the work organized from observation to delivery.
This guide describes the connected platform. Screenshots are earlier trial and interface captures illustrating the controls; visible values and availability labels belong to those captures.
01 / PC NET DESK
A desktop for
the work behind the site.
Keep the tools you need open together. Review a task, inspect an interface, and reach the next control from the same workspace.
Familiar controls.
Less searching.
- What it does
- Launches the management apps in movable windows, with minimize, maximize, close, a taskbar, notifications, and desktop personalization.
- How it works
- The desktop shell opens individual app views. Window controls manage the workspace around those tools; the apps retain their own content and actions.
- Why it matters
- Related work can stay visible together. You spend less effort finding the right page and rebuilding context between tasks.
Explore screenshot ↗The right tool within reach
The launcher groups website editing, connected reporting, operations, and administration. Open the relevant tool directly, then keep related tools in view as the work develops.
Personalization with a purpose
Desktop backgrounds, appearance, and settings are separate from the public website’s design. Change your working environment without confusing it with the customer-facing page.
02 / CORE CONSOLE
Find the signal.
Act on the detail.
A structured dashboard for the website and its surrounding work, with a command line for supported tasks that are faster to type.
Explore Core Console ↗FROM INFORMATION TO ACTIONReview Organize Control See the complete capability directory ↗
Owner Summary, traffic, search, marketing, and website activity give the workspace its analytical structure.
Tasks, calendar events, approvals, notes, forms, and reports turn observations into recorded work.
Styles, content tools, scheduled changes, and administrative controls provide routes to action.
The dashboard is the interface
Choose a module from grouped navigation to work on one subject at a time. Desk offers a windowed alternative to this focused dashboard.
Connected reporting, useful context
First-party visits, GA4, search, campaign activity, calls, and competitor research give the dashboard its reporting depth. Source and period context help explain what each measure means.
One operation, two entry points
The authenticated command interpreter calls the same backend functions as the supported visual tools. That reduces duplicated behavior between clicking and typing.
THE COMMAND LINE INSIDE CORE CONSOLE
Direct, deliberate control.
Commands such as tasks, calendar, calls, and help retrieve supported information. Authorized commands can also update task status, notes, forms, and approvals.
The interpreter accepts a defined vocabulary. It does not provide an unrestricted server shell. Visual work—such as choosing an image—stays in the visual tools.
READ
tasksLEARNhelp taskACTtask done <id>Examples above describe the authenticated command registry. The GCI preview has its own local command set; use its help command for exact syntax.
Inspect the command interface ↗CONNECTED WEBSITE ANALYTICS
Every visit.
More context.
Who arrived, where they came from, what they explored, how long they stayed, and what they clicked. Core Console brings the signals together so you can understand the journey and decide what to improve.
Who visited?
Review visitor groups, first and latest activity, return visits, device, browser, and operating system. Available network enrichment adds approximate location and organization context; an inquiry can supply actual contact details.
Useful for: understanding your audience and recognizing continued interest.
How visitor recognition works
First-party records group matching network and browser context. Connected analytics supplies its own visitor and session identifiers. A company or network match does not identify every person, and shared networks or changing devices can affect grouping.
Where did they come from?
See search, paid campaigns, social, referring websites, direct traffic, and recognized AI referrals. Referrers and campaign tags connect an arrival with its source, medium, campaign, and landing page.
Useful for: finding the channels that bring relevant attention.
How attribution works
The site records referrer and campaign context; connected acquisition reports organize it by channel. Search Console adds aggregate queries and search visibility. Missing source information remains direct or unknown; it does not become a guessed referral.
What did they look at?
Follow landing pages, service pages, products, FAQs, proof, and contact pages in the order recorded. See which topics attract attention and where the observed visit ends.
Useful for: understanding interests and improving the route to an inquiry.
How the journey is assembled
Page paths and timestamps establish the sequence of recorded activity. Session reports add entrances and exits within their measurement window. Individual paths show behavior; page-level comparisons show broader patterns.
How long did they look?
Review session duration and measured engagement at the page and event level. Compare a brief arrival with deeper interaction, and compare the same page across devices or sources.
Useful for: seeing where content holds attention or needs a clearer next step.
What time measurements mean
Connected analytics calculates duration and engagement from the events it receives. Elapsed session time and active engagement are different measures. A recorded duration does not prove that someone read every word or kept looking at the screen.
What did they click?
Track instrumented buttons, links, phone and email actions, downloads, outbound destinations, and form activity. The page and event context show which next steps attracted a response.
Useful for: improving calls to action and locating friction before conversion.
How actions become useful signals
Website events record the supported action, location, destination, and time. Reports distinguish a click from a successful form submission or provider-recorded call, so interest is not counted as a completed inquiry.
Why were they here?
Interpret the combination of source, landing page, reading path, engagement, and actions. A service-to-FAQ-to-contact journey may suggest evaluation; a direct visit to support information may suggest an existing need.
Useful for: answering the questions visitors appear to be asking.
Observed behavior, inferred purpose
The platform records activity. Intent is a reasoned interpretation of that evidence, strengthened by what a visitor actually says in an inquiry. A page view alone does not establish budget, urgency, identity, or a decision to buy.
READING A VISITOR JOURNEYFrom a traffic source
Illustrative journeyFrom a traffic source
to a useful next step.
- ARRIVALSearch or referral
Source · campaign · landing page
- EXPLORATIONService page
Page view · engagement · next page
- EVALUATIONFAQs and evidence
Sequence · return activity · clicks
- RESPONSEContact action
Button click · submission or call
A visit reaches a service page, continues to FAQs, and uses the contact action. The source, page order, engagement measures, and event record describe that activity.
The visitor may be evaluating that service. Make the explanation, trust signals, and contact route easy to find; use an actual inquiry to understand the person’s need.
Collect the activity
First-party page records capture visits and context. Connected analytics and instrumented events supply engagement and interactions. Call and form records complete the response picture.
Put the signals in context
Read page activity alongside traffic sources, campaign reports, geography, devices, and search performance. Keep each source’s definitions and reporting period visible.
Turn insight into work
Find the unclear page, weak next step, or missing answer. Record a task, improve it in the Builder, publish the change, and review the next reporting period.
COMPETITOR ANALYSIS & ANALYTICS
See the market.
Find your opportunity.
Compare how other businesses are found, what they offer, and how they present themselves. Bring those findings back to the pages, messages, and experiences you control.
A CONSISTENT COMPARISONFive lenses.
Five lenses.
Clearer priorities.
Connected research combines public website information, search data, review signals, and third-party estimates. Compare the same market and time period, and keep the source attached to the finding.
Turn an opportunity into a page ↗| Research lens | What you compare | What it helps you decide |
|---|---|---|
| Search visibility | Queries, ranking pages, topic coverage, and estimated visibility. | Which questions and search opportunities your pages should address. |
| Service coverage | Services, industries, locations, and the depth of public explanations. | Where to build a useful service, location, or audience page. |
| Positioning | Messaging, offers, evidence, and calls to action. | How to make your own value and reasons to choose you clearer. |
| Reputation | Public ratings, review volume, and recurring review themes. | Which concerns to answer and which credible proof to make visible. |
| Website experience | Mobile presentation, navigation, content clarity, and consistent review criteria. | Which usability and presentation changes deserve priority. |
Keep the evidence traceable
Your own analytics describes activity on your site. Competitor research describes public observations and third-party estimates. Those sources answer different questions and should retain their labels.
Look for a specific gap
A missing explanation, a confusing service choice, an unanswered question, or weak proof is actionable. A broad comparison score becomes useful when the underlying reason is clear.
Close the loop
Record the opportunity, create the work, and use the Builder and Style Engine to deliver it. Measure the effect on your own site’s acquisition, engagement, and inquiries.
03 / WEBSITE STYLE ENGINE
A whole visual language.
At your fingertips.
Change the feel of a website through coordinated settings for theme, color, typography, icons, backgrounds, scale, and motion.
Inspect the style controls ↗Many choices.
One coordinated result.
- What it does
- Applies a design family, then lets you refine individual design decisions without manually editing each component.
- How it works
- A saved style record supplies shared values to the website’s theme styles and effects. The website reads those settings as it renders; previews show the selected treatment.
- Why it matters
- Shared settings keep common elements visually consistent. Separate website records make it possible to restyle a selected site without changing every other site.
DefaultWindows 11iOSAndroidUbuntuSoft UI
Color beyond a single accent
Built-in palettes coordinate primary and secondary colors. Custom schemes can also define backgrounds, surfaces, panels, borders, muted text, and body text for light and dark appearances.
Type and icons, independently
A theme supplies a starting point. Fonts and icon families can be selected separately, so the site’s typographic voice does not force a particular icon treatment.
Control the reading experience
Desktop and mobile backgrounds, dimming overlays, reading glass, scroll blur, and element sizing help balance the visual treatment with legibility.
Motion with adjustable behavior
Ten effects cover linked networks, falling data, circuits, pulsing hexagons, moving packets, warp starfields, auroras, radar sweeps, perspective grids, and signal ripples. Adjust intensity, amount, density, speed, strength, colors, and supported pointer, click, or double-click responses.
Different screens, visible previews
Mobile and desktop previews render the page at different widths. Light and dark preview controls help reveal problems before applying a treatment.
Separate the site from the workspace
Website Style Engine, Core Console Style, and Desk Style target different surfaces. A presentation choice for visitors does not have to dictate how the operator’s tools look.
Enlarge ↗
Enlarge ↗
Enlarge ↗
Enlarge ↗04 / WEBSITE BUILDER ENGINE
From a working draft
to a page of its own.
A structured creation engine for service, campaign, location, and audience pages. Edit content, assemble supported sections, design the experience, and publish an independent page.
Compose
Select a field from the editor or click text in the preview. Edit headings, body copy, cards, FAQs, buttons, and supporting content.
Arrange
Add, duplicate, remove, and reorder supported repeated items. Reorder the middle sections while keeping Hero and Contact at the ends.
Preview
The authenticated editor renders the website in draft scope, using the same page components and text-fitting behavior as the site.
Publish
Choose a valid name. Publish content, structure, style, and logo as an independent snapshot at /published/name.
A deliberate separation
between editing and publishing.
Saving a draft gives you a place to work. Publishing copies that draft into a specific page’s saved snapshot. Editing the next draft does not silently rewrite the last published page.
The URL selector lists existing published targets. Replacing one asks for confirmation and affects that target’s snapshot. The main homepage continues to read its separate live content.
That makes the Builder useful for producing variations and dedicated pages from a consistent website system.
Structured freedom
The Builder edits the supported website components. Contact identifiers, business metadata, and every possible layout are not unrestricted drag-and-drop fields.
Inspect the content editor ↗
Enlarge ↗
Enlarge ↗INSIDE THE WEBSITE BUILDER ENGINE
A page system
you can work with.
The engine connects an editable field registry, reusable components, design settings, and published records. Each layer solves a different part of building a complete page.
Content with a defined place
Headings, lead text, body copy, button labels, FAQs, and cards have registered fields. Search the field list or select supported text in the preview. Length and text-fitting constraints help the finished copy fit its component.
The advantage: edit the right message with the layout in view.
Structure from reusable components
Add, duplicate, remove, and reorder supported navigation items, badges, service cards, chips, products, nested bullets, and FAQs. Collection limits protect the layout. Reorder middle sections while Hero stays first and Contact stays last.
The advantage: build depth and change the story without recreating the page framework.
Design stored with the draft
Choose the theme, palette, typography, icons, backgrounds, sizes, and effects from the Style tab. Upload the logo and control its supported header and footer visibility. Preview the treatment at desktop and mobile widths.
The advantage: content, layout, and brand can be refined together.
A preview using the website itself
The editor renders the site’s components with draft content, structure, design, and logo state. Shared rendering and text-fitting behavior keep the preview tied to how the website is built.
The advantage: evaluate the page as a visitor will encounter it before publishing.
A publication with its own saved state
Choose a valid name or an existing destination. Publishing copies the draft into that page’s content, structure, style, and logo records at /published/name. Replacing an existing destination asks for confirmation.
The advantage: the next draft can evolve without silently changing the last published page.
ONE ENGINE, SEVERAL USESGive a specific audience
Give a specific audience
a more useful page.
- Service pagesExplain one offer, its benefits, evidence, and next step.
- Campaign pagesKeep the message consistent from the referring campaign to the page.
- Location pagesUse relevant service-area copy and useful local context.
- Audience pagesArrange the supported content around a particular need or industry.
WEBSITE AUTOMATIONS
Plan the change.
Let the schedule handle it.
Prepare a supported website setting, choose its value and time, and let PC NET DESK apply it when due. Use one-time changes or repeat them daily or weekly.
32
Supported website settings.
From the visual theme to how a background responds to a pointer, each action targets a defined setting with a validated value.
Theme and color
Switch the website’s design family or color scheme for a planned presentation change.
Desktop and mobile backgrounds
Control background images and visibility independently for the two screen contexts.
Readability
Enable the desktop or mobile dimming overlay and set its strength.
Motion and interaction
Set the effect, colors, intensity, amount, density, speed, strength, and mobile behavior; adjust supported pointer, click, and double-click responses.
A PRACTICAL AUTOMATION
A planned seasonal treatment.
Prepare the presentation ahead of time, then give the beginning and end their own scheduled actions.
- PREPAREChoose the setting and value
Give the action a meaningful name and select the registered website setting.
- STARTSchedule the new treatment
Set a date and time, choose one-time execution, and enable the action.
- RESTORESchedule the original value
Add a second action for the end of the period. The first action does not imply an automatic undo.
A record you can inspect
Each action holds its name, setting, value, scheduled time, repeat rule, enabled state, and last-run information. Edit, disable, or delete it as the plan changes.
A runner that applies due work
The platform checks for due actions during website or Console rendering, with a one-minute throttle per running instance. A 15-minute heartbeat also checks during quiet periods. Due values are saved and the settings cache is refreshed.
A schedule that moves forward
Execution records the last-run time. Daily and weekly actions advance to their next due time. When multiple due actions change the same setting, the later scheduled value takes precedence.
AI-READY. CREATED FOR AGENTS.
A workspace for people.
A clear interface for agents.
PC NET DESK was created to be used by agents. Named commands, structured records, explicit editing scopes, and shared backend functions give an agent a way to understand the work, take a defined action, and verify the result.
CORE CONSOLE / AGENT WORKFLOW27 COMMAND FAMILIES
help task
tasks
task done <record-id>
tasksDiscover the operation. Read its target.
Make the authorized change. Verify the result.
Shared behavior, two ways in.
The command interpreter calls the same functions as the supported visual apps. An agent can perform a defined operation and a person can inspect it in the workspace.
Precise targets for useful work.
Field IDs, record IDs, component groups, typed settings, and draft/published scopes tell an agent what it is changing. The Builder separates preparation from publication.
Knowledge an agent can read.
The technical reference documents the command and API contracts, data model, source files, and operating constraints. A JSON catalog and plain-text guide provide the same knowledge in directly consumable forms.
Agent interfaceCommands, identity, errors and verification ↗JSON catalogCapabilities, schemas and technical inventories ↗Agent referencePlain-text discovery and operating guide ↗
Agents use authorized browser sessions and supported operations. A dedicated agent adapter can connect those operations to an AI system; the reviewed source does not bundle a model, an MCP server, or an autonomous planner.
WHY THE PARTS BELONG TOGETHER
Understand. Improve.
Keep the work moving.
Consider a new service page. Connected insight identifies the need, the creation tools shape the response, and the workspace keeps delivery and follow-up in view.
- 01CORE CONSOLE
Identify the need
Review visitor paths, search demand, campaign response, and competitor gaps in Core Console. Find the question or service that deserves a clearer page.
- 02DESK + CONSOLE
Record the work
Create a task, add a date, and record an approval decision where the workflow needs one.
- 03BUILDER + STYLE
Build a coherent page
Use the Builder’s supported content and sections. Refine the page’s visual treatment with its style controls.
- 04WEBSITE BUILDER
Publish deliberately
Review the draft, select the destination, and publish the authenticated Builder’s independent snapshot.
- 05CORE CONSOLE
Review what changed
Record the delivery and review sources, page engagement, clicks, and actual inquiries. Compare consistent periods and use the findings to plan the next improvement.
THE COMPLETE CAPABILITY DIRECTORY
What it does.
How. And why.
100 capabilities, organized by the work they help you do. Open any entry for its mechanism, practical purpose, and relevant operating detail.
A connected platform, explained.
Reporting entries describe connected data sources. Website entries explain the supported editing and publishing controls. Scheduled actions describe changes the website can apply from a saved schedule.
No capabilities match. Try a broader term or clear the search.
Workspace & everyday tools
10 CAPABILITIESPC NET DESKA desktop workspace for website operations, reporting, and everyday work.Workspace
How it works
The browser desktop launches management apps in movable, resizable windows with a shared launcher, taskbar, and notifications.
Why it is useful
Keeps the information and controls for related work visible together.
App launcher & window controlsFind apps and manage what is on screen.Platform feature
How it works
Grouped app shortcuts open windows; controls move, resize, minimize, maximize, close, and snap them. The browser remembers supported window layouts.
Why it is useful
Lets the operator choose between a focused full-size app and several visible tools.
Desk & Core Console SettingsManage the operator’s workspace preferences.Workspace
How it works
Dedicated settings control the desktop and dashboard separately from the public website. Export, import, and reset tools manage supported workspace records.
Why it is useful
Makes the workspace comfortable to use while keeping visitor-facing design decisions separate.
NotificationsReview supported workspace and access updates.Workspace
How it works
The notification tray combines access activity, new leads, detected AI crawler activity, and change-log updates. Selecting an event opens its related app, and a local seen-state distinguishes new activity.
Why it is useful
Makes changes discoverable while the operator works in other tools.
Photo Gallery & CameraCapture, upload, and reuse images.Media tools
How it works
The gallery accepts uploaded media and browser-authorized camera captures, then makes supported images available to the platform’s editing and appearance tools.
Why it is useful
Keeps reusable imagery close to the pages and designs that need it.
Asset LibraryOrganize logos, images, icons, and documents.Media tools
How it works
The library groups reusable files and references by type for discovery and selection.
Why it is useful
Gives brand material a consistent home and reduces repeated uploads.
Web BrowserOpen a website from a contained workspace view.Platform feature
How it works
An embedded browser view loads destinations that allow embedding, with an external-tab route where available.
Why it is useful
Keeps reference material close to the work while respecting the destination’s own access and framing rules.
Installable website, Console & DeskLaunch the three experiences as separate installed web apps.Workspace
How it works
Separate web manifests provide stable app identities, icons, start URLs, and standalone presentation for the public website, Core Console, and PC NET DESK. Installation support depends on the browser.
Why it is useful
Makes a frequently used workspace easier to find and open from the device.
Installation describes the app shell; it does not promise an offline copy of live administrative data.
Saved window layouts & preferencesReturn to a familiar arrangement of work.Workspace
How it works
Browser-local storage remembers window positions, sizes, minimized and maximized states, appearance preferences, and notification read state. Layout persistence is separate from shared business records.
Why it is useful
Reduces repeated setup while keeping each operator’s device comfortable to use.
Mobile workspace behaviorUse the same apps on a smaller screen.Workspace
How it works
Desk presents apps at full screen on mobile and disables desktop drag, resize, and snapping behavior at that size. Website background and appearance controls also distinguish desktop from mobile.
Why it is useful
Preserves usable controls and reading space across devices.
Analytics, search & marketing
15 CAPABILITIESOwner SummarySee website performance and operational priorities together.Connected reporting
How it works
Connected reporting supplies headline traffic, inquiry, marketing, and health indicators; detailed modules explain the activity behind the summary.
Why it is useful
Provides a useful starting point for deciding what deserves attention.
Lead TrackingTrack inquiries, their sources, and their progress.Connected reporting
How it works
Connected inquiry records bring source, date, contact context, and stage into a reviewable lead view.
Why it is useful
Shows which channels generate inquiries and what needs follow-up.
Conversion FunnelFollow the journey from arrival to inquiry.Connected reporting
How it works
Connected stage totals compare visits, service-page interest, contact-page activity, and recorded calls or form submissions over the selected period.
Why it is useful
Reveals where people progress and where the path needs improvement.
First-party AnalyticsReview recorded website visits and visitor context.Connected reporting
How it works
The site records page paths, timestamps, referrers, and browser context. The reporting layer groups related visits and enriches network records with available location and organization information.
Why it is useful
Makes the site’s own activity available beside the tools used to improve it.
AI AnalyticsTrack detected AI crawlers and visits referred by AI services.Connected reporting
How it works
Recorded agent activity is classified separately from human referrals; recognizable referrers and campaign information identify supported AI traffic sources.
Why it is useful
Shows how machine discovery and AI-driven referrals contribute to site activity.
A crawler visit shows access; it does not establish that an AI answer recommended the business.
Google Analytics 4Review acquisition, engagement, page activity, and events.Connected reporting
How it works
Connected GA4 reports supply users, sessions, engagement measures, sources, devices, landing pages, and instrumented events.
Why it is useful
Connects acquisition quality with what visitors actually do after arriving.
Search ConsoleTrack search queries, visibility, clicks, and page performance.Connected reporting
How it works
Connected search reporting compares impressions, clicks, click-through rate, position, queries, and pages across reporting periods.
Why it is useful
Identifies pages to improve and the search demand they could serve.
Search queries describe aggregate search performance; they are not a transcript of each individual visitor’s searches.
Service PagesCompare attention and response across services.Connected reporting
How it works
Page-level reporting associates service paths with visits, engagement, and recorded inquiry actions.
Why it is useful
Helps prioritize services and page improvements using observed interest.
GeographicSee where website attention comes from.Connected reporting
How it works
Connected reports group activity by available country, region, and city estimates, with source and page context where available.
Why it is useful
Supports service-area planning and content suited to the markets attracting attention.
SEO OpportunitiesTurn search performance into a list of improvements.Connected reporting
How it works
Search indicators and page comparisons highlight opportunities such as improving titles, answering questions, and deepening useful service content.
Why it is useful
Connects visibility gaps with concrete work for the content and website tools.
Meta / Facebook AdsReview paid campaign delivery and response.Connected reporting
How it works
Connected campaign reports show spend, reach, impressions, clicks, leads, and cost per lead for the reporting period.
Why it is useful
Makes paid traffic accountable to the website activity and inquiries it produces.
Social OrganicTrack the reach and response of organic social content.Connected reporting
How it works
Connected social reporting brings follower trends, reach, engagement, and post performance into the same review environment.
Why it is useful
Helps connect publishing effort with the topics and channels that attract interest.
Call TrackingInclude telephone inquiries in acquisition reporting.Connected reporting
How it works
The call-provider connection supplies recorded call activity and attribution for comparison with website and campaign reporting.
Why it is useful
Makes phone response visible alongside forms and other digital inquiries.
A phone-link click and a provider-recorded call are different events.
Website HealthReview the website’s operational condition.Connected reporting
How it works
Connected checks report availability, links, forms, tracking, indexing, sitemap, certificate, and page-speed findings.
Why it is useful
Brings technical problems into the same workflow as content and marketing improvements.
Competitor SnapshotCompare competitors’ visibility, services, reviews, and website presentation.Connected reporting
How it works
Connected competitor research organizes public information and third-party estimates into a consistent comparison, with a source and reporting period for interpretation.
Why it is useful
Helps prioritize credible differentiation and useful content improvements.
Competitor traffic estimates are distinct from your own first-party analytics; this does not expose competitors’ private visitor records.
Visitor intelligence
08 CAPABILITIESVisitor profilesUnderstand who is visiting at the level the available evidence supports.Visitor intelligence
How it works
Visit records group network and browser context, first and latest activity, and the paths seen. Identified inquiry records provide contact context when someone supplies it.
Why it is useful
Distinguishes anonymous interest from an actual known inquiry.
A network or organization match is not a verified personal identity; shared networks and changing devices affect grouping.
Company, location & deviceSee the setting behind a visit.Visitor intelligence
How it works
Network enrichment supplies available organization and approximate geography; browser context supplies device, operating system, and browser.
Why it is useful
Helps assess service-area fit and the experience visitors receive on different devices.
Traffic sources & campaignsTrack where visitors came from.Visitor intelligence
How it works
Referrers and UTM campaign parameters feed source and medium reporting across search, paid campaigns, social, referrals, direct, and recognized AI sources.
Why it is useful
Shows which channels bring useful attention rather than just volume.
Direct or unknown traffic is retained when the source cannot be established.
Page paths & journeysSee the pages a visitor viewed and their order.Visitor intelligence
How it works
Timestamped page records and connected session reports reveal entrances, subsequent pages, repeated views, and exits within the observed visit.
Why it is useful
Shows the routes people take through services, proof, FAQs, and contact information.
Time & engagementMeasure how long visits and page interactions last.Visitor intelligence
How it works
Connected session and event reporting supplies duration and measured engagement time at the available session and page level.
Why it is useful
Helps separate a brief arrival from a visit involving deeper interaction.
Elapsed time and active engagement measure different things; neither proves that every word was read.
Clicks, events & conversionsTrack the interactions that move a visitor forward.Visitor intelligence
How it works
Instrumented events record supported link and button clicks, phone and email actions, downloads, outbound links, and form activity with page and event context.
Why it is useful
Reveals which calls to action work and where interest stops short of an inquiry.
A click, a successful submission, and a completed call remain distinct outcomes.
Return visits & continued interestRecognize repeat activity in the available reporting window.Visitor intelligence
How it works
First-party grouping and analytics identifiers expose repeat activity where the browser and collection context allow it.
Why it is useful
Helps identify topics attracting continued attention and compare new with returning engagement.
Cross-device visits or cleared identifiers do not automatically resolve to one person.
Intent analysisInterpret why a visitor may have come.Visitor intelligence
How it works
Source, landing page, page sequence, time, and actions provide evidence for an operator’s intent assessment, such as researching a service or seeking support.
Why it is useful
Turns activity into a useful hypothesis about what the website should explain next.
Intent is inferred from behavior; the visitor’s stated purpose is stronger evidence.
Competitor intelligence
04 CAPABILITIESSearch & content gapsCompare discoverability and useful topic coverage.Market intelligence
How it works
Connected search research and public-page reviews compare queries, ranking pages, and content coverage for a consistent market and period.
Why it is useful
Finds questions and topics that deserve a better answer on your own site.
Services & positioningReview how alternatives describe their offer.Market intelligence
How it works
Compare public service pages, locations, audiences, offers, evidence, and calls to action in a structured competitor view.
Why it is useful
Helps make your own service proposition clearer and more distinctive.
Reviews & website experienceAssess trust signals and the experience competitors present.Market intelligence
How it works
Public ratings, review themes, navigation, mobile presentation, and a consistent website-review rubric support like-for-like comparisons.
Why it is useful
Turns competitive research into specific improvements to clarity, credibility, and usability.
Research to actionConnect a competitive gap to a website improvement.Market intelligence
How it works
Record the finding, create the follow-up task, develop a Builder page or content change, and review your own connected results after publication.
Why it is useful
Makes competitive analysis useful to delivery instead of leaving it as a disconnected report.
Public observations and third-party estimates do not reveal a competitor’s private traffic, customers, or conversion performance.
Work & reporting
08 CAPABILITIESFormsReview inquiries and record follow-up.Connected workflow
How it works
Submission records support status changes and private notes, with matching commands for supported actions.
Why it is useful
Keeps an inquiry’s current state and next action together.
Tasks / To-doCreate, complete, and remove work items.Platform feature
How it works
Editable task records are read from the configured collection; the command registry also supports adding, completing, reopening, and removing them.
Why it is useful
Makes the next action explicit and allows supported visual and textual workflows to use the same records.
Approval CenterRecord a review decision.Platform feature
How it works
The pending queue supports approve and reject actions on its records; matching authenticated commands call the same status update functions.
Why it is useful
Keeps decisions attached to a defined item instead of relying only on an informal conversation.
An approval record does not by itself mean that website publishing is automatically gated by that approval.
CalendarPlan dated work and milestones.Workspace
How it works
Event records place deadlines and scheduled work inside the same workspace as the tools used to deliver them.
Why it is useful
Keeps upcoming work visible while making changes and reviewing results.
Clock & heartbeatInspect time and automation-runner activity.Operations
How it works
The clock shows working time; recorded heartbeat timing helps explain when the scheduled-action runner last checked for due work.
Why it is useful
Gives the operator context for schedule execution and troubleshooting.
Monthly ReportsReview performance across reporting periods.Connected reporting
How it works
Connected monthly-report records preserve period summaries for comparison with the underlying traffic, marketing, and operational information.
Why it is useful
Builds a review history that makes changes and priorities easier to discuss.
Strategy / Client NotesKeep decision context and priorities available.Workspace
How it works
The notes editor reads and saves persistent written context within the platform.
Why it is useful
Preserves the reasoning behind a decision alongside the metrics and tasks.
Change LogReview recorded changes and releases.Operations
How it works
Dated entries carry a version, change type, and description for operational review.
Why it is useful
Helps relate a website change to subsequent behavior or performance.
Website & design
17 CAPABILITIESWebsite Style EngineControl the look of the selected website.Platform feature
How it works
A per-website style record drives theme, scheme, icon, font, background, sizing, and effect settings.
Why it is useful
Coordinates many components from a shared set of decisions and preserves the selected website’s scope.
Website BackgroundChoose separate images for desktop and mobile.Platform feature
How it works
Background controls draw from built-in and uploaded images. The style system supports per-page overrides and a return to the site default.
Why it is useful
Allows the composition to fit the screen and the page rather than forcing one image everywhere.
Welcome MessageUpdate the website’s introductory message.Website engine
How it works
A focused editor changes the designated welcome or hero message for its assigned website.
Why it is useful
Makes a frequent content adjustment quick to find and perform.
Website BuilderEdit a structured draft and publish a named page.Website engine
How it works
The Builder saves content, repeaters, section order, design, and logo state. Publication creates or replaces the selected page’s independent snapshot.
Why it is useful
Supports dedicated pages while keeping work in progress separate from published content.
Color Scheme BuilderCreate and reuse coordinated palettes.Platform feature
How it works
The source supports named custom schemes with brand and neutral color values, including separate light/dark and website/console settings.
Why it is useful
Avoids repeating a collection of individual color choices every time a treatment is reused.
Core Console StyleTune the dashboard’s own appearance.Platform feature
How it works
Console-specific theme and presentation settings operate separately from website style settings.
Why it is useful
Lets the operator optimize the working interface without changing the public-facing brand experience.
Desk Style & Desk BackgroundCustomize the desktop shell.Platform feature
How it works
Dedicated controls manage the desktop theme, accent, icons, type, backgrounds, and supported effects.
Why it is useful
Keeps desktop personalization independent from the site and the dashboard.
Six visual familiesChange the character of the website or workspace.Design engine
How it works
Default, Windows 11, iOS, Android, Ubuntu, and Soft UI each provide a coordinated CSS treatment. Website, Core Console, and Desk can have independent selections.
Why it is useful
Provides a coherent starting point instead of styling every component separately.
Independent typography & icon familiesFine-tune identity within a chosen theme.Design engine
How it works
Five font families and six icon families can be selected independently. Fonts use the registered web or system font stacks; the icon renderer maps the same semantic icon to its selected family.
Why it is useful
Retains consistent meaning while changing the visual voice.
Light, dark & custom neutral colorsKeep both color modes intentional.Design engine
How it works
Eight built-in palettes and custom schemes define five brand color roles. Custom neutral sets control background, surface, panel, border, muted copy, and text for website and Console light/dark contexts.
Why it is useful
Keeps brand accents, surfaces, and reading contrast coordinated.
Ten animated background effectsGive a page a controlled sense of motion.Design engine
How it works
Network, Rain, Circuit, Hex, Packets, Warp, Aurora, Radar, Grid, and Signal share adjustable intensity, amount, density, speed, strength, and two colors; Off disables the effect.
Why it is useful
Makes a distinctive presentation reusable without editing animation code.
Pointer, click & touch responsesControl how an effect reacts to the visitor.Design engine
How it works
Attract, Spawn, Repel, and Trail can be combined. Separate settings govern pointer parameters, click or tap responses, double-click boosts, and whether the effect runs on mobile.
Why it is useful
Lets the operator balance interaction, motion, and the needs of different devices.
Reusable effect presetsSave a motion treatment and use it again.Design engine
How it works
Named presets store a validated effect configuration. Apply a preset to the selected website, Console, or Desk surface; delete presets that are no longer needed.
Why it is useful
Reduces repeated tuning and makes a preferred treatment reproducible.
Mobile reading glass & scroll blurAdjust the background as the reader moves through a page.Design engine
How it works
At widths up to 980 pixels, two independent scroll-driven effects use an ease-out ramp. Controls set activation, ramp distance, maximum opacity, and maximum blur for the reading overlay and background blur.
Why it is useful
Keeps the opening view expressive while making longer reading more comfortable.
Component size controlsAdjust the density of supported page elements.Design engine
How it works
Six size settings scale service, product, and Why Us cards, chips, badges, and FAQ items from 60% to 180%. CSS variables coordinate padding, icon size, and radius within each element type.
Why it is useful
Changes visual emphasis while retaining the component’s proportions.
Per-page background inheritanceGive a registered page its own background.Design engine
How it works
The Contact page currently supports desktop and mobile image overrides. Removing an override restores the selected website background. Developers can register more pages in the same system.
Why it is useful
Creates page-specific identity with a clear fallback to the site-wide design.
Console panels, header & menu surfacesTune the structure around the work.Design engine
How it works
Default, flat, glass, and gradient treatments expose a color and opacity for Console panels, header, and menu surfaces. Desk has its own appearance settings and starts from Console defaults until overridden.
Why it is useful
Makes the operator’s workspace legible and personal without changing the public website.
Website Builder engine
10 CAPABILITIESField selection & text fittingEdit the website’s registered content in context.Website engine
How it works
Click supported preview text or search the field list, then edit within the field’s length and fit constraints. Shared rendering applies the site’s text-fitting behavior.
Why it is useful
Makes content easier to find and reduces layout problems caused by oversized copy.
Repeaters & nested contentBuild out cards, lists, navigation, products, and FAQs.Website engine
How it works
Supported collections expose add, duplicate, delete, and reorder controls; nested product bullets and collection size limits preserve the component structure.
Why it is useful
Expands a page without rebuilding every repeated item by hand.
Section orderArrange the body of the page around its purpose.Website engine
How it works
Move supported middle sections while Hero remains first and Contact remains last.
Why it is useful
Allows a different narrative while preserving a predictable entrance and response point.
Design & logo controlsGive the draft a complete visual identity.Website engine
How it works
The Builder’s Style tab controls logo upload and visibility, theme, palette, font, icons, backgrounds, sizing, and effects.
Why it is useful
Keeps content and visual refinement in one editing context.
Draft scope & rendered previewReview a page before exposing the next version.Website engine
How it works
The draft keeps content, structure, style, and logo state together and renders the site’s components in preview scope.
Why it is useful
Shows how the actual website system treats the work before publication.
Named pages & snapshotsPublish a dedicated page at a chosen destination.Website engine
How it works
Choose a valid page name or an existing target. Publication copies the draft into independent records at /published/name; replacing a target asks for confirmation.
Why it is useful
Supports service, campaign, location, and audience pages with deliberate replacement and separate published state.
A registered content modelEdit a known part of the page with predictable rules.Builder engine
How it works
The base schema defines 124 text fields in ten sections. Each field has a stable ID, visual role, label, original copy, line and character limits, and allowed text scale. Added repeater items receive their own field identities.
Why it is useful
Gives people and agents precise targets and keeps text fitting tied to its actual component.
Bounded components & directional movementRearrange supported groups without losing their structure.Builder engine
How it works
Ten groups define the allowed item types and minimum/maximum counts. Grid-based groups support row-aware movement, product cards contain one to eight nested bullets, and six middle sections can be reordered between the fixed Hero and Contact sections.
Why it is useful
Allows meaningful composition while protecting the layout’s basic shape.
Text restoration with a defined scopeReturn copy to its original wording.Builder engine
How it works
Restore one registered text field or reset all editable text. Original copy lives in the schema; item deletion and order belong to the separate structure model.
Why it is useful
Makes a copy reset understandable and avoids treating it as a whole-site rollback.
Content boundaries & shared structured dataKeep editable copy consistent with the page’s behavior.Builder engine
How it works
The Builder edits registered copy and components. Business contact channels, metadata, form labels, and animated stat numbers have separate implementation controls. Product wordmarks are editable through their repeater fields. FAQ output uses the same resolved content for visible answers and structured data.
Why it is useful
Protects functional details and reduces disagreement between visible content and machine-readable answers.
Website automations
04 CAPABILITIESScheduled setting changesPrepare changes to 32 supported website settings.Scheduled actions
How it works
Each action selects a registered theme, palette, background, readability, motion, or interaction setting. Typed validation checks its value before storage.
Why it is useful
Makes automated changes explicit and predictable.
One-time, daily & weekly schedulesChoose when a website setting should take effect.Scheduled actions
How it works
The action stores its scheduled date and time and an optional daily or weekly repeat rule; recurring actions advance to their next due time after running.
Why it is useful
Supports planned launches and recurring presentation routines.
Action managementControl the schedule as plans change.Scheduled actions
How it works
Name, edit, enable, disable, or delete an action; inspect its next scheduled time and last-run information.
Why it is useful
Makes upcoming work visible and lets an operator pause or revise it.
Execution & heartbeatApply due changes and leave an execution record.Scheduled actions
How it works
The runner checks enabled actions during website or Console renders, throttled to once per minute per running instance. A 15-minute heartbeat covers quiet periods, applies due values, refreshes settings, and records last-run time.
Why it is useful
Balances reliable checks with a lightweight system that does not need a continuously running scheduler.
These actions target the main website’s registered settings. Builder publishing is a separate action; this scheduler changes registered website settings.
Administration & automation
11 CAPABILITIESUsersReview authorized users and provision ordinary platform accounts.Administration
How it works
The administrator supplies a name and email. The system reserves a seat, creates or reuses a Wix member, approves and authorizes it, and requests a set-password email. The reviewed implementation caps authorized accounts at ten; a new account does not become an administrator.
Why it is useful
Gives access a deliberate owner, a visible capacity limit, and a repeatable onboarding path.
Email acceptance is recorded separately from delivery. A failed provisioning attempt does not grant access.
Recent AccessReview administrative access history.Administration
How it works
Access records expose timestamps and outcomes for inspection.
Why it is useful
Supports investigation and accountability with a usable event history.
Security & Emergency LockControl access to administrative tools.Administration
How it works
Member checks, allowlists, configured passkey enforcement, IP policy, alerts, and Emergency Lock support the platform’s administrative access rules.
Why it is useful
Restricts sensitive operations and gives the administrator controls for responding to access concerns.
AutomationsSchedule supported website settings to change.Scheduled actions
How it works
A saved action contains a setting, validated value, scheduled time, repeat rule, and enabled state. The due-action runner applies the change and records execution.
Why it is useful
Handles planned and recurring presentation changes without a manual visit at every scheduled time.
Console command interpreterUse defined commands for supported operations.Platform feature
How it works
A fixed registry validates commands and dispatches to the same functions used by supported authenticated tools. It is not an operating-system shell.
Why it is useful
Provides a direct route for repeated tasks without adding arbitrary code execution.
FilesBrowse the implementation from the workspace.Administration
How it works
The Files app lists build-bundled source files and opens their text through an authorized, read-only endpoint. It does not browse the live server filesystem or edit deployed code.
Why it is useful
Lets maintainers and authorized agents understand the implementation behind an interface without leaving the workspace.
Build NotesKeep architecture and operating knowledge accessible.Administration
How it works
An in-platform documentation view provides implementation, setup, and operating notes.
Why it is useful
Preserves the knowledge needed to maintain and extend the system.
Passkey registration & device managementUse a device-backed credential for protected access.Administration
How it works
WebAuthn registration and verification pair browser credentials with server challenges and stored public-key records. Authorized controls list, rename, and revoke passkeys; the administrator can enable enforcement.
Why it is useful
Supports strong sign-in without asking an agent or operator to handle a reusable password for every action.
IP access policyManage the network addresses allowed by the configured policy.Administration
How it works
The security view exposes validated IP entries and an enable switch. Server and administrative access flows apply their implemented identity and policy checks.
Why it is useful
Gives the administrator an additional control for the intended operating environment.
Denied-access alertsMake rejected access attempts visible.Administration
How it works
Supported access flows record denied attempts, expose unacknowledged alerts, and use configured notification settings. The administrator can acknowledge reviewed alerts.
Why it is useful
Turns access concerns into reviewable activity instead of relying on someone noticing an error screen.
Emergency Lock & recoveryPause protected changes during an incident.Administration
How it works
Emergency Lock is checked by protected mutations and the scheduled-action runner. Its explicit recovery flow can lift the lock; the public lead form remains available.
Why it is useful
Creates a way to interrupt administrative changes while continuing to accept business inquiries.
Demonstration & presentation
04 CAPABILITIESDemo ModeWalk through the platform’s feature surface.Platform feature
How it works
The demonstration interface guides the viewer through selected panels and explanatory steps.
Why it is useful
Introduces the system without requiring the viewer to know its navigation first.
Presentation ModePresent the workspace as an organized story.Platform feature
How it works
A presentation surface provides a sequential walkthrough with navigation and supported voice options.
Why it is useful
Connects features to their purpose during a demonstration.
Voice ModeRead supported interface summaries aloud.Presentation
How it works
Browser speech synthesis uses device voices and user-controlled playback.
Why it is useful
Offers an optional spoken route through the platform explanation.
About PC NET DESK & Core ConsoleUnderstand the platform’s purpose and feature surface.Workspace
How it works
The About app introduces the workspace, its capabilities, and its operating model.
Why it is useful
Helps a new operator understand the system before exploring individual tools.
AI readiness & agent workflows
09 CAPABILITIESCreated for people and agentsGive software agents understandable ways to operate the platform.Agent-ready design
How it works
The design pairs visual tools with registered text commands, structured records, explicit scopes, and inspectable source. Agents can work through an authorized browser session and supported command routes.
Why it is useful
Lets an agent translate a task into named operations and explain the result in the same terms as a human operator.
Discoverable command vocabularyFind the supported operations before acting.Agent interface
How it works
The help command lists 27 command families; help followed by a command explains its syntax. Double quotes keep multi-word arguments together.
Why it is useful
Reduces guesswork and makes repeatable tasks easier to plan.
A JSON command contractSubmit a defined operation and read its result.Agent interface
How it works
An authenticated POST to /api/cc/console accepts a command string and returns output lines plus an isError flag. Commands are limited to 500 characters; the technology reference documents the exact response behavior.
Why it is useful
Provides a small, explicit integration surface that an authorized agent adapter can use.
Shared visual and command behaviorReach the same underlying operation in two ways.Agent interface
How it works
Registered commands call the functions used by the supported visual modules. Operations such as task status, notes, approvals, forms, and due-action execution reuse the platform’s data layer.
Why it is useful
Reduces the chance that clicking a control and issuing a command produce different business behavior.
Typed targets & explicit scopesTell an agent exactly what can change.Agent interface
How it works
Stable field IDs, component group IDs, value registries, record IDs, and live/draft/published scopes describe the target of a change. The Builder keeps content, structure, style, and logo state separate.
Why it is useful
Supports precise edits, easier review, and a clear explanation of the affected state.
Authorized agent operationCarry the operator’s access rules into automated work.Agent interface
How it works
Agent use of administrative surfaces requires the appropriate member identity, permissions, and applicable passkey or lock checks. A browser session or separately implemented adapter supplies that context.
Why it is useful
Keeps automation tied to an accountable identity and the operation’s actual access rules.
Read, act & verifyCheck the outcome before reporting completion.Agent workflow
How it works
Read the current record, issue one scoped operation, inspect HTTP and command error information, then read the affected record or page again. A timed-out write needs a state check before a retry.
Why it is useful
Helps an agent avoid duplicate work and distinguish a successful request from the intended result.
Machine-readable referenceLet an agent consume the same feature and technical model as a reader.Documentation
How it works
This guide provides a JSON catalog and a plain-text agent reference containing capability explanations, command syntax, schemas, API descriptions, and operating constraints. The files are read-only documentation.
Why it is useful
Makes discovery and handoff easier without requiring an agent to infer contracts from screenshots.
AI discovery & traffic visibilityUnderstand how AI systems encounter the website.Connected reporting
How it works
Public content and structured FAQ data make the site readable; llms.txt offers a discovery summary. AI Analytics separates recognized crawler activity from supported AI referral traffic.
Why it is useful
Connects machine discovery with observable visits while keeping agent operation and traffic measurement distinct.
THE SCREEN TOUR
Look closer.
Explore the interfaces.
18 interface captures, from the desktop and Console to the Style Engine and Builder. Select a screen to enlarge it. Captured September 2026; each screen retains its trial or preview source label.
View full screenshot ↗The app launcherPublic Sennett trial
View full screenshot ↗A working desktopPublic Sennett trial
View full screenshot ↗Desk settingsPublic Sennett trial
View full screenshot ↗Desktop appearancePublic Sennett trial
View full screenshot ↗Core Console overviewGCI browser preview
View full screenshot ↗The command interfaceGCI browser preview
View full screenshot ↗Tasks and next actionsGCI browser preview
View full screenshot ↗The working calendarGCI browser preview
View full screenshot ↗Website and color controlsPublic Sennett trial
View full screenshot ↗Typography and iconsPublic Sennett trial
View full screenshot ↗The mobile website previewPublic Sennett trial
View full screenshot ↗Readability and sizingPublic Sennett trial
View full screenshot ↗The background libraryPublic Sennett trial
View full screenshot ↗The welcome-message editorPublic Sennett trial
View full screenshot ↗The Console app directoryGCI browser preview
View full screenshot ↗Website Builder: contentBuilder source preview
View full screenshot ↗Website Builder: designBuilder source preview
View full screenshot ↗The local drafting previewGCI browser preview
BUILT AROUND THE WHOLE JOB
Insight becomes direction.
Direction becomes a better website.
Know what needs attention.
Visitor journeys, acquisition, search, marketing, health, and competitor research give decisions a basis in recorded activity and traceable information.
Explore visitor intelligence ↗Make the next version useful.
The Builder connects structured content, design, preview, and publication. The Style Engine applies coordinated visual choices across the selected website.
Explore the Builder Engine ↗Keep the work moving.
Tasks, approvals, notes, reports, and scheduled website changes bring delivery and ongoing improvement into one working environment.
Explore website automations ↗Interface tour: screenshots retain their public trial, browser-preview, and Builder-source labels. The guide describes the connected platform; the values shown in earlier captures are illustrative. Explore selected styling controls in the public trial ↗