A website visitor directions brief helps a business turn an address into useful arrival instructions. A map pin can identify a neighbourhood while leaving a first-time visitor unsure about the gate, entrance, floor or reception desk. Those details matter when a Kenyan organisation expects customers, suppliers or appointment holders to visit.
Discuss the arrival journey with your website developer in Kenya before approving a contact-page map. The public address, visible instructions and destination link should agree. The aim is to help someone reach the appropriate public entrance without exposing private staff details or promising facilities that have not been verified.
This guide concerns one business's practical visitor information. It is not a template for creating near-identical location pages, a local ranking promise or a substitute for checking the actual site.
Establish whether visits are welcome
Start by describing the service arrangement. Can people walk in, must they book first, or is the location used only for a particular activity? An office address does not automatically mean a public reception or collection service exists. Have the responsible person approve the wording before it is added to the website.
Separate the reasons for visiting where necessary. A meeting entrance may differ from a goods-delivery point. If the business uses both, label the instructions according to the visitor's task rather than displaying two unexplained map links beside the same address.
Record the public location name, responsible owner and last verification date. Keep a private internal reference if it helps staff manage the record, but do not publish operational details simply because they were collected in the worksheet. The page should contain the information a visitor actually needs.
Verify the pin against the entrance
Ask someone who knows the site to open the proposed map destination and check it. Confirm the location name and the route to the appropriate entrance. A pin placed somewhere within a large building or compound may still be insufficient for someone arriving from the road.
Record any useful final approach in plain language. A visible sign, gate name or reception floor can help, provided it is accurate and stable. Avoid depending entirely on a nearby landmark that may change or be unfamiliar to the person visiting.
Review the destination on a phone as well as a desktop browser. Check what opens when the visitor chooses directions and whether the displayed place is the one the business intended. Ask the developer to distinguish the website's link from the routing suggestions provided by the external map service.
Choose an appropriate map presentation
Google's Maps Embed documentation describes different map modes, including place and directions. Use that distinction to discuss whether the page needs to identify a destination, show an area or offer a route. The implementation should follow the task rather than inserting a map merely to fill space.
Ask the developer to explain the proposed external service and any configuration responsibilities. Keep credentials and account access in the approved secure process, outside the public content worksheet. Do not copy a working embed from another organisation and assume it represents your own location correctly.
Provide the address and essential instructions as readable page text as well. If the external map cannot load, someone should still be able to identify where to go and how to contact the business. Review that fallback directly instead of assuming every visitor will have the same map application or browser settings.
Write the final approach as a short sequence
Describe the last part of the journey in the order a visitor needs it. They may need to identify the building, choose the correct entrance and report to a named public desk. Keep the explanation short enough to use while standing outside with a phone.
Separate permanent directions from temporary instructions. An entrance used during construction may need an expiry or review date. If the temporary route is placed inside a permanent paragraph without ownership, it can remain online long after it stops being useful.
Use an approved photograph only when it answers a practical question. An entrance image may help someone recognise the gate, while an attractive interior photograph may not. Follow the website image content brief to record what the picture shows, why it belongs and who approves its use.
Confirm hours and appointment conditions
Record the hours applicable to the visit being described. General office hours, customer reception times and a collection window can differ. Use clear labels rather than one ambiguous opening-hours statement that staff later have to explain over the phone.
State any booking condition before the visitor begins travelling. Link to the relevant enquiry or appointment route where one exists, and make clear whether a submitted request is awaiting confirmation. Do not describe every form submission as a confirmed meeting.
Assign an owner for holiday changes, closures and unusual access arrangements. The owner should know all places the instructions appear, including contact pages and confirmation messages. Updating one page is insufficient when an older email template still sends people to a different entrance or time window.
Describe access information from verified facts
Ask the site team which arrival details can be stated accurately. This may include steps, a lift, a reception procedure or an alternative contact route. Avoid using broad labels such as fully accessible without an appropriate assessment and clearly defined meaning.
If a visitor may need assistance, provide an approved public contact method and explain when to use it. Do not publish a staff member's private number simply because that person usually helps with arrivals. Give the support team enough information to handle the request through the business's normal channel.
Coordinate evaluation with the website accessibility brief. The website's operability and the physical site's access arrangements are related visitor concerns, but they require different evidence. A readable directions page does not establish that every physical journey is suitable for every person.
Review common changes and exceptions
Prepare instructions for a moved office, a changed entrance and a temporarily unavailable reception. Decide who approves the update and how urgent corrections reach the website team. Keep the public explanation proportionate rather than exposing internal disputes or operational details.
Check old references when a location changes. Printed QR codes, directory entries and appointment messages may still direct people to the previous address. Record the references your team controls and the external ones that require a separate correction request.
Where an old website address no longer exists, use the missing-page recovery brief to decide its treatment. Do not leave a visitor with contradictory directions merely because the new page has been published successfully.
Test an arrival without insider knowledge
Ask a reviewer unfamiliar with the location to follow the written instructions in a controlled review. They should identify the intended place, entrance and next step using the page. Record ambiguous wording and incorrect destinations without requiring a real customer to make a wasted trip.
Check the phone layout, copyable address and map link. Review a case where the embedded map is unavailable and confirm that the essential information remains readable. If a contact form is involved, use an agreed test environment rather than creating synthetic live enquiries.
Keep the verified location sheet and update responsibilities in the website handover. Request a website development quotation with the arrival content, map presentation and review process included. Clear information and accountable maintenance are more useful than a map graphic approved once and then forgotten.
Frequently asked questions
Is a map pin enough for an office inside a compound?
Check the actual approach. Include approved entrance and reception instructions where they are needed, and verify the public destination on a phone.
Should a home-based business publish its private address?
The business owner should decide what public visitor arrangement exists. Do not publish a private location merely because it appears in an internal project record.
Can directions include parking or step-free access claims?
Use only facts the responsible team has verified and can maintain. Avoid broad facility promises inferred from a photograph or an old listing.
Who should approve changed hours?
Name an operational owner and a backup. Record the related pages and messages so a correction reaches all visitor instructions under your control.
