Start with the fact your team can confirm.
Your website says you are closed on a particular Monday. A listing shows your usual Monday hours. A customer cannot tell whether to visit, call or wait. Copying whichever version looks newest could spread the wrong answer.
Pick one disputed detail and establish the current fact with the person responsible for it. For a special closure, that might be the confirmed operating schedule. For a contact link, it might be the business’s approved public destination. Record the source and date checked before proposing edits.
This is an accuracy check for public business information, not a recommendation to create more listings. Only use platforms and profile types your business qualifies for. Do not invent an office, service area, business name, category or opening hours to fill a field.
Compare like-for-like information.
On a small screen, swipe or scroll sideways to read the full table.
| Detail | What to establish | What not to assume |
|---|---|---|
| Opening hours | Regular hours, a special closure or the hours of a particular service. | A one-day change replaces the recurring weekly schedule. |
| Business location | The truthful customer-facing location or permitted service-area presentation. | A service area is a staffed office, or a private home address should be published. |
| Phone or contact route | The approved public number or destination and the team that receives it. | A number displayed on a page proves routing works or a response will arrive. |
| Website or booking link | The intended destination, service and visible next step. | An opening page proves a form, booking or payment completes correctly. |
| Business name and description | The actual public identity and an accurate description of what is available. | Extra locations or services can be added simply to attract more searches. |
Different fields can legitimately have different values. A website footer may use the legal company name while a profile uses the appropriate public business name. A contact number may have an intentional routing purpose. Record why a difference exists before treating it as an error.
Follow a special-closure example.
Fictional example: a local studio usually opens Mondays from 9 to 5. Its owner confirms that it will be closed on one specific Monday for planned maintenance. A notice on the website already explains the dated closure, but a business listing still displays normal hours.
- Record the dated closure and owner-confirmed source. Keep the normal weekly schedule separate.
- Check how the listing supports special hours or a dated closure. Give the authorized profile editor the exact proposed change and date.
- Record when the edit was submitted and any status shown. Do not label it publicly corrected while the platform is still reviewing it.
- Check the customer-facing result after the edit is accepted. Does it describe the intended date without making every Monday appear closed?
- Assign a follow-up check after that date. Confirm the ordinary schedule still reads correctly and remove or update any expired website notice through the normal editing process.
Google distinguishes regular, special and additional service hours and reviews Business Profile edits before they go live. Other platforms have their own controls and rules. Use the current instructions for the profile you actually manage.
Separate an edit from its visible result.
For each surface, keep these steps distinct: observed mismatch → proposed correction → authorized edit → submitted → publicly verified. If a change is rejected or still pending, record that state and the responsible next step. Do not keep submitting different versions just to see which one sticks.
Check the public view rather than relying only on the editor. Note the URL, observation time and the specific field reviewed. A dated screenshot can document that observation; it does not prove the information will remain unchanged everywhere.
When checking a link, opening the destination can establish that it loads and describes the right action. It is not an end-to-end test. Do not create a customer inquiry, appointment or payment merely to complete this checklist. Any operational test needs a separately agreed plan and permission.
If the facts agree but the website and booking page make different promises, use the customer-promise check. That is a different problem from an incorrect number or opening time.
Leave a record the next editor can use.
Download the blank public-business-details worksheet (CSV). One row represents one field on one public surface. Use the business’s approved information only; do not put login details, private addresses or customer information in the sheet.
Start with a field that can change a customer’s next action: an incorrect closure, unusable contact route or wrong booking destination. For every unresolved row, name the editor or owner and a reasonable next check. A platform review may take time; a submitted edit is still unfinished work.
Keep the current fact and the source that supports it in the team’s answer library. Revisit affected surfaces when hours, contact routes or service availability change. This is more useful than repeatedly checking unchanged pages without a reason.
Current reference: Google’s guidance on editing Business Profile information. Platform eligibility, field availability and review outcomes depend on the actual business and platform. Accurate details help a customer understand the next step; this checklist makes no ranking promise and does not establish listing management as an included BusinessOS service.
Explore Make the public version match the real business. for related questions and a useful starting point.