Say which side of the river you cover before the visitor has to guess
In a metro split across three jurisdictions, coverage is the first question in a buyer's head and most sites answer it last.
Someone in Silver Spring who cannot tell within a few seconds whether you work in Montgomery County will leave. So will someone in Old Town looking at a site that reads as District-only. The header and the first screen should carry the jurisdictions plainly, in words, not as a map graphic that fails on a phone.
Say it specifically. The District, Montgomery County, Prince George's, Arlington, Alexandria, Fairfax County. Naming places is more credible than saying you serve the DMV, and it filters out the inquiries you cannot take.
Put license numbers by jurisdiction in the footer and on a credentials page. Requirements differ across the three, and buyers here, many of whom evaluate vendors for a living, will look.
If your coverage has edges, publish them. A short line saying where you do not go saves your estimators more time than any lead magnet on the site.
A rowhouse page and a subdivision page cannot be the same page
The two dominant housing types in this market need separate pages because the work, the constraints and the buyer's worries are all different.
The rowhouse page talks about masonry openings that are rarely square, custom sizing, wood double-hung units, working from an alley, protecting a shared wall, permit parking, and what happens in a designated historic district. Photographs should be of narrow lots and brick facades.
The subdivision page talks about standard openings, whole-house pricing, efficiency and noise, and a schedule measured in days rather than in access negotiations. Different photos, different sequence, different objections handled.
Route to them early. A visitor who selects their house type in the first screen gets a page that reads as though it was written for them, which is the whole point.
Condo and high-rise units in places like Navy Yard or Tysons are a third path if you serve them, because approval sits with an association and the visitor needs to know you have dealt with that before.
Ask for alley access and a photo of the window before you ask for a phone number
The inquiry form is a qualification tool for this trade, and the fields that matter here are not the ones on a stock template.
Property address first, because it establishes jurisdiction and housing type at once. Then approximate number of openings, what the windows are now if the owner knows, and whether the property is a rowhouse, a detached house, a townhouse or a unit in a building.
Add an access question. Whether there is off-street parking or alley access sounds like an odd thing to ask a homeowner and it is the single most useful field on a District form. It sets expectations and it tells your scheduler what kind of day this will be.
A photo upload is worth more than three more text fields. One picture of the window and its surround tells an estimator most of what a phone call would.
Keep the form short enough to finish standing in a cold room on a phone. Everything you add costs completions, so every field has to earn its place by changing what you would do next.
Work in a historic district is proof, and proof belongs above the gallery
For a Georgetown or Capitol Hill owner, evidence that you have completed permitted work in a designated district outranks every other trust signal on the site.
Show the work with the neighborhood named and, if you can, what the constraint was. A photograph of a completed rowhouse elevation with a sentence about what had to be matched does more than a badge row.
Describe process without promising outcomes. In most cases review requirements depend on the district and the visibility of the elevation, and it is worth confirming with the relevant historic preservation office. Say that you handle the filing and the coordination if you do. Never state that a project will be approved.
Keep testimonials to things you can actually document. Do not publish claimed approvals, association endorsements or product ratings you have not confirmed in writing.
Place the proof high. It should sit above the general project gallery, because it is the specific reassurance the highest-value District visitor came looking for.
A photo-heavy portfolio on a weak signal loses to a plain page that loads
Install photography is your best sales asset and the most common reason these sites are slow on the device most buyers use.
Your visitor may be in a basement, on a Metro platform, or in an old brick rowhouse where the signal is poor. A gallery of full-resolution images and three embedded third-party widgets will not finish loading before they give up.
Compress and size images properly, serve modern formats, and load anything below the first screen lazily. The hero image should be prioritized and small enough to appear almost immediately.
Audit the scripts. Chat widgets, review carousels, financing calculators, heat mapping and multiple analytics tags each cost load time. Keep the ones that demonstrably produce booked work and remove the rest. Most sites in this trade are carrying at least two nobody remembers installing.
Test on a real phone on a throttled connection, not on office wifi on a laptop. The gap between those two experiences is where the inquiries go.
Publish license numbers by jurisdiction and nothing you cannot document
A buyer pool trained in procurement diligence will check what you claim, and an unsupportable claim costs more than the sale it was meant to win.
State your licensing by jurisdiction with numbers, and keep them current. Insurance certificates on request. Manufacturer certifications only where you hold them.
Leave out efficiency savings figures, rebate eligibility promises, and any statement that a product will satisfy a code or review requirement. Rebate programs change, and eligibility is generally worth confirming with the administering program or the reader's own tax advisor.
Do not publish before-and-after images that have been retouched, and do not show work you did not perform. In neighborhoods this small, someone will recognize the house.
Say what you do not do. If you do not repair sashes, if you do not work above a certain height, if you do not serve a jurisdiction, put it in writing. Owners here respond well to a firm that draws its own boundaries.
Questions we actually get
- Do we need a separate landing page for every neighborhood we serve?
- No. Build pages around the things that genuinely differ: jurisdiction, housing type, and product line. A Georgetown page is justified if you have historic district work to show and something specific to say about it. A page that only swaps the neighborhood name into the same paragraphs will not rank and will not persuade anyone who reads it.
- How many fields should the inquiry form have?
- Few enough to complete on a phone and specific enough to qualify. Address, approximate opening count, property type, access, and a photo upload will do more work than a long form. Every additional field reduces completions, so each one has to change what you would do next. If a field does not affect scheduling or pricing, cut it.
- Should we put pricing on the site?
- Ranges, with honest conditions, generally outperform silence with buyers here, many of whom evaluate vendors professionally and dislike being made to call for a number. Say what moves the price: opening count, whether the openings are standard, masonry versus frame, access, and whether a permit or review is involved. Do not publish a number you cannot honor.
- Is a chat widget worth the load time it costs?
- Sometimes, if it is actually staffed during the hours it appears. An unstaffed widget that replies the next morning is worse than no widget, because it absorbs the contact and delays it. Measure whether it produces booked measures. If it does not, removing it usually buys back noticeable speed.
- Can we show projects we worked on as a subcontractor?
- Only with the permission of whoever holds the relationship, and only described accurately. Presenting subcontracted work as your own project is the kind of claim that gets checked in a small market. If your role was the install, say the install was yours.
