Overview
When setting up a Local GBP Playbook, you may find that one or more of your Google Business Profile projects do not appear in the project selection dropdown — even though your GBP accounts are already connected. This article explains what to check on your end and what happens when the issue requires backend intervention from our team.
Step 1: Verify Your GBP Project Is Connected
Before anything else, confirm that the affected Google Business Profile is properly connected inside the platform.
- Navigate to the GBP Projects section within the Local area of the platform.
- Review the list of connected projects and confirm that the GBP you expect to appear in the Playbook is listed there.
- If it is not listed, use the option to connect or add your Google Business Profile account and follow the on-screen prompts.
- Once connected, return to the Local GBP Playbook and check whether the project now appears in the selector.
Step 2: Confirm All Relevant GBPs Are Visible
If you manage multiple locations or brands under the same account, make sure you are looking at the correct workspace and that all GBP accounts have been connected — not just some of them. It is possible for one location to appear while another does not if the connection step was only partially completed.
- Check that each individual GBP location you need appears as its own entry in the GBP Projects section.
- If a location is listed in GBP Projects but still missing from the Playbook selector, the issue is likely a backend configuration problem rather than a missing connection.
Step 3: What to Do If the Project Is Connected but Still Missing
Based on confirmed cases, a GBP project can be fully connected yet still fail to appear in the Local GBP Playbook selector due to a missing internal project link. This requires a backend fix applied by our support team and cannot be resolved by reconnecting the GBP or adjusting settings on your end.
If you have completed Steps 1 and 2 and the project is still not appearing, contact our support team directly so a specialist can identify the missing internal link and apply the necessary backend fix. Once the fix is applied, the project will appear in the Playbook selector without any further action needed on your side.
Tips to Avoid This Issue
- Always connect a GBP account through the GBP Projects section before attempting to configure a Playbook for that location.
- If you are setting up multiple locations, connect and verify each one individually before building out Playbooks.
- After connecting a new GBP, allow a few moments for the platform to register the project before navigating to the Playbook selector.
Still Not Resolved?
If your GBP project is confirmed as connected in GBP Projects but still does not appear in the Local GBP Playbook selector, a backend fix is required. Please reach out to our support team via the chat widget so a specialist can resolve this for you as quickly as possible.