Start by asking Alexa about your business by name, branch and town. Record the answer and check whether the result identifies a data provider. I could not verify a universal Amazon submission form that adds every local business to Alexa. The practical route depends on which business, location and provider the answer actually identifies.
Test three different questions
Ask where the business is, when it closes today and what number to call. A correct address alongside incorrect hours is more useful evidence than a broad complaint that the business is missing. Try the full trading name and neighbourhood. A category search such as “nearby bakeries” measures discovery, which is different from whether Alexa knows your exact shop.
Try the exact trading name, then a category query and finally a request for opening hours. A customer asking for your shop by name is doing something different from someone asking for a nearby repair shop. Write down which query failed and the location the device used.
Correct the source record
Look up the named provider’s public listing. Claim the existing branch through its official owner process where available, rather than creating a duplicate. Match the customer-facing name, street address, local phone number and opening hours to the business website. Pay particular attention to holiday hours and branches with nearly identical names.
Compare your storefront name, street address, phone number and hours across records you actually control. A duplicate listing for a previous location can explain a wrong answer even when the current listing is correct. Keep a note of which record you changed and when.
Understand what building a skill does
Amazon documents LocalBusiness intents for developers who build voice experiences. Those intents describe questions about addresses, hours or contact details. They are not a business registration form. After correcting a listing, repeat the same questions from the same location and record the date. No specific update window or search position is guaranteed.
For the documented details, see LocalBusiness developer reference.
Building a custom skill gives people a named experience to invoke. It does not establish that general nearby-business queries will recommend your shop. Decide whether customers need directions and opening hours or a genuinely interactive service before investing time in a skill.
Investigate a wrong open-now answer
Check the day of the week, the device’s location and any holiday exception. A shop may have a regular Saturday schedule and a different festival closing time. Correct the exception in the relevant listing, then repeat the original question. Record the spoken answer rather than relying on your memory of an earlier result.
Separate a naming problem from a location problem
If the exact name finds the shop but a category search fails, changing the name to a string of keywords is a poor diagnostic. Verify the business category and test from a device in the service area. If the result instead points to an old branch, focus on the address and duplicate record.
Keep a short test log
Use columns for the phrase spoken, test location, date, returned business and error. A correction is successful when the original failing request gives the right fact. One correct reply does not guarantee placement in every generic recommendation; track accuracy separately from prominence.
Common questions
Should I pay for guaranteed placement?
Ask for verifiable terms. A directory edit cannot guarantee Alexa’s recommendation.
What if Alexa names the wrong branch?
Repeat the query with the neighbourhood or street.
Do I need to sell on Amazon?
A seller account is for commerce and does not establish a local listing.
What if no provider is shown?
Use Alexa feedback with the exact query and corrected public details.