Three people read this site: the owner, their designer and the building manager
The homeowner starts the search, but the decision passes through people who are looking for entirely different evidence.
The owner wants to see finished work and to feel that strangers in their home for months will be bearable. The designer wants scope, workflow and whether you take direction. The manager or board member wants licensing, insurance, references from comparable buildings and a sense that you will not create a complaint file.
Give each of them something visible in the first screen. A one-line statement of what you do and where, proof that the work happens inside occupied buildings in Miami-Dade, and a route to credentials that does not require hunting.
Cut the generic opener. Craftsmanship, family-owned and serving South Florida since are all true of every competitor and answer none of the three questions being asked.
Then put a short, plain page about your process inside a managed building somewhere obvious in the navigation. It is the page the designer forward, and the page a manager skims before replying to an owner's email.
A building index does more work than a services menu
Organize the site around the places you have worked rather than the products you install.
Kitchens, bathrooms, cabinetry and countertops as top-level navigation tells a reader nothing they did not assume. Where you have worked tells them everything, particularly in a market where capability is measured building by building.
Structure it as an index of completed work grouped by area, with the tower and mid-rise projects distinguished from single family work in Coral Gables or Coconut Grove. Each entry gets what happened: the scope, the constraints you worked around, how access and hours were handled.
Only publish entries you can back up. An index padded with buildings you have never entered will be spotted by exactly the designer whose opinion you needed.
This structure also gives the rest of the site somewhere to point. Area pages, service pages and any Spanish content all link into real projects rather than into a stock photo carousel.
Ask for the building and the floor, not the square footage
For tower work the inquiry form is a logistics form, and the fields that matter are the ones nobody asks for.
Building name, unit floor, whether they own the unit or are still buying, whether the association's renovation packet has been requested, whether plumbing or walls are moving, and rough timing. Those six answers tell you more about whether this is a real job than any budget dropdown.
Keep the visible form short and pick up the remainder in the confirmation step or the first call. A long form on a phone is an abandoned form.
Add a photo upload. Owners take pictures of the space and of the association letter, and both arriving with the inquiry can save a week.
Make the confirmation useful rather than polite. Tell them what happens next, roughly when, and what to have ready. The gap between submitting and hearing back is where doubt does its work.
The Spanish site needs its own URLs and its own phone routing
A translation widget is not a Spanish website, and in Miami-Dade the difference is commercial rather than cosmetic.
Client-side translation leaves nothing indexable, produces phrasing that reads as machine output, and often mangles the one thing that has to be right, which is the form.
Publish real pages on their own URLs with correct language annotations, written by somebody who writes Spanish natively for this market. Terminology varies by community, so the wording is a decision, not a default.
Route the inquiry properly. A Spanish form should trigger a Spanish confirmation and reach somebody who can continue in Spanish, including after hours. Otherwise the site is generating conversations the business cannot have.
Do not let the language switcher throw people back to the homepage. Someone reading a project page wants that page in the other language, not a fresh start.
Chat widgets and review scripts slow a site more than photographs do
Most slow remodeling sites became slow after launch, one bolted-on script at a time.
A chat bubble, a review carousel, two analytics tools, a heatmap recorder and a tag manager holding all of them will outweigh a well-handled gallery. Audit what is loading before touching image quality.
Handle the images properly and then leave them alone: modern formats, sizes matched to the layout, lazy loading below the fold and a priority hint on the one image in the first screen. Galleries should load progressively rather than in one heavy burst.
Test on a real phone on a real connection. Site owners judge speed on a desktop over office wifi, and the people you care about are standing in a lobby or a lift.
One practical note. If you are keeping only a couple of third-party tools, keep the ones that produce evidence, which usually means call tracking and analytics, not the ones that produce decoration.
Publish the kitchen, never the unit number
What you show about somebody's home carries more risk in a market of towers and non-resident owners than in a subdivision.
Get written permission before publishing photographs of anyone's home, and keep it on file. Owners who agreed verbally two years ago change their minds when a project appears in an ad.
Leave out anything that identifies the unit: unit numbers, floor plans with location markers, views that pin the exact stack, and any detail about access, keys or security arrangements.
Be careful with wording about buildings. Describing work you completed in a building is a statement of fact. Describing your firm as approved or endorsed by a building or its association is a claim you generally should not make unless they have put it in writing.
If you also publish about exterior or site work, note that the City of Miami is zoned under Miami 21 and that designated historic districts including Morningside, Buena Vista East and Spring Garden carry their own review through the Historic and Environmental Preservation Board. Requirements vary and change, so write generally and tell readers to confirm with the building official or their own counsel.
Questions we actually get
- How many project pages do we need before the site is worth publishing?
- Fewer than you think, if they are detailed. A handful of properly written projects with real constraints and real photographs will do more than thirty thin entries. Publish what is genuine and add to it as jobs finish.
- Should the site show prices?
- Not a price list, but a posture. Saying plainly what kind of project you take on, and that you work at the considered end rather than the quick-turnaround end, filters inquiries before they reach the phone. Vagueness attracts the inquiries you least want.
- Do we need a separate Spanish site or separate pages?
- Separate pages on the same site is the normal approach: their own URLs, their own language annotations, natively written copy. A wholly separate site doubles the maintenance and usually ends up half-updated within a year.
- Can we publish photographs of a job if the owner is happy but the building never gave permission?
- Owner permission in writing is the baseline and should always be obtained. Beyond that, avoid identifying the unit and avoid any wording that suggests the building or its association endorses your firm. Where a building's own rules or your contract touch on publicity, it is worth confirming with your own counsel.
- Is a chat widget worth having?
- Only if a human answers it quickly. An unattended widget adds weight to every page and teaches visitors that nobody is home. If the phone gets answered reliably and the widget does not, remove the widget.
