> ## Content Index
> Fetch the complete content index at: https://gothru.co/blog/llms.txt
> Use this file to discover other available public pages before exploring further.

# Google Street View photos not showing in your tour?
- URL: https://gothru.co/blog/review-google-street-view-photos-not-showing-tour/
- Published: 2026-10-12T11:10:22.000Z
- Updated: 2026-10-12T11:10:22.000Z
- Description: Troubleshoot a missing panorama in a connected, published GoThru Street View tour. Check the public route, GoThru status, and the affected image before retrying.
- Author: Alin Bugeag
- Tags: 360 Virtual Tour, Virtual Tour Software, 360 Photography

After I publish a connected tour, I open it on Google Maps and follow the route. If navigation stops before the next panorama, I check whether that image is visible at all. A missing panorama needs a different check from a visible panorama with missing arrows.

I filmed the repair on a tour with about 200 panoramas. Six were missing from Google. In the video, I use GoThru Street View Status to find the affected images, change their starting viewpoints, and test the route again. That is one tour, not a guaranteed repair for every missing Street View image.

## First, check which image is missing

I don't change a published tour until I've found the point where it stops. These checks keep me from trying to repair a panorama when the real problem is a connection or a Maps display issue.

| What I see                                      | What I check next                                                                                                                                                                              |
| ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A blank Maps screen or older imagery            | I check another browser or device and the imagery date. That view alone doesn't tell me my published panorama was rejected.                                                                    |
| A new panorama has not appeared                 | I check when it was published and look at its status in GoThru before attempting a repair.                                                                                                     |
| The route stops and the next panorama is absent | I compare that gap on public Maps with the affected image in Street View Status.                                                                                                               |
| Both images appear, but the arrows are missing  | I check the connection. The separate guide to [missing Street View navigation arrows](https://gothru.co/blog/google-street-view-navigation-arrows-missing-after-publishing/) covers that case. |

If you're looking for a regular photo you contributed to a Maps place, check that contribution in your Google account and on the public listing. The repair below is for panoramas in a connected GoThru tour. If you have not published the tour yet, follow the [tour publishing guide](https://gothru.co/blog/create-google-360-virtual-tour/) first.

## Check the public route and allow for processing

I open the published tour on Maps and note the last panorama I can reach. Then I look for the next image on its own. If it appears independently, I investigate the connection instead of deleting the image. I also check the public view while signed out when I need to distinguish it from what my own account shows.

In my video, I check Street View Status after about 30 minutes on a smaller tour or closer to an hour on a larger one. Those are the times I chose to check, not Google deadlines. [Google says links between Photo Spheres published with a third-party tool can take up to four days to process](https://support.google.com/maps/answer/7012050?hl=en&ref=gothru.co). That applies to links. It does not promise that an upload marked rejected will appear after four days.

## Find the affected panoramas in GoThru

I open the tour's **Street View Status** and compare it with the gap I found on Maps. In the tour shown in the video, six panoramas are missing from Google and appear as **Map Rejected** in GoThru. When I select **Edit 360 Images**, GoThru marks them in magenta so I can locate each one.

![GoThru Street View Status map with magenta panorama markers and a color-coded status legend](https://gothru.co/blog/content/images/2026/10/street-view-status-map-and-legend.webp)

*Street View Status in the walkthrough. The map and legend help locate images that need a closer check. This is a GoThru screen, not a public Maps result.*

Map Rejected is the label I see in GoThru for a panorama that Google received but did not accept for map display. It isn't the name of every Google publishing error. Google's [Street View Publish API describes publication status and panorama connections separately](https://developers.google.com/streetview/publish/reference/rest/v1/photo?ref=gothru.co). I still check the public route because a status label won't tell me whether navigation has recovered.

![GoThru Edit 360 Images card with a magenta marker and AI Map Rejected tooltip](https://gothru.co/blog/content/images/2026/10/rejected-panorama-edit-card.webp)

*An affected panorama in Edit 360 Images. The tooltip reads "AI Map Rejected" in this capture.*

If all the panoramas in a tour are affected, I use the separate [all-panoramas Map Rejected guide](https://gothru.co/docs/how-to-fix-a-tour-where-all-panos-are-map-rejected/?ref=gothru.co). I wouldn't delete an entire tour to address one missing transition.

## Recenter a panorama rejected by mistake

Google doesn't give me a precise explanation of what its automated review detected in each image. I have seen skin-like colors in posters, human-shaped art, curved walls, and long hallways in panoramas that appear to have been rejected by mistake. These are my observations, not Google's published rejection rules. I use this method only when the image itself complies with Google's policies.

Before I remove a rejected Google copy, I make sure the source panorama is still available in my GoThru tour and identify the exact image that is missing. Then I follow the sequence shown in the video.

1. I use the image's three-dot menu to delete the rejected copy from Google.
2. I open the **Image Centering Tool** in GoThru.
3. I rotate the panorama so the suspected trigger is no longer in the initial view, then apply the new center.
4. I republish the affected images and return to **Street View Status** after Google processes them.

![GoThru Image Centering Tool dialog showing a panorama, center guide, and Apply button](https://gothru.co/blog/content/images/2026/10/image-centering-tool-dialog.webp)

*The Image Centering Tool in the walkthrough. This shows the control before the repair is applied, not a successful Google Maps result.*

Recentering changes the initial viewpoint. It does not remove anything from the 360 image. The [GoThru Map Rejected repair guide](https://gothru.co/docs/how-to-fix-maps-rejected-panoramas-using-gothru/?ref=gothru.co) covers another repair path, although its screenshots may show an earlier interface. Check the controls in your account before deleting a Google copy.

## Test the image and the connection separately

After republishing the six affected panoramas in the video, I check Street View Status again after about 10 to 15 minutes. Five are accepted after my first recentering attempt. That result and timing belong to this tour. I cannot promise the same outcome for another image.

I return to the exact spot where navigation stopped. I check whether the image appears on Maps, then try the transition. Sometimes I can see a panorama before its navigation links are ready. I give published links time to process and check the connection again. If the image is still absent, I inspect its status before retrying rather than republishing blindly.

## What I do when recentering is not enough

One panorama in the video remains rejected because I cannot find an initial view that avoids the areas I suspect. I use a selective blur on the affected part of that image, apply it in Moderator, republish, and check again. The current [GoThru blur guide](https://gothru.co/docs/how-to-blur-using-new-ai-moderator/?ref=gothru.co) covers selecting and applying a blur. I review the result before republishing, especially when faces or license plates need privacy protection. Blur is not a way around Google's content policy.

When Google shows a specific **publishing failed** message, I read the error instead of treating it as Map Rejected. [Google's troubleshooting guide](https://support.google.com/maps/answer/9972052?hl=en&ref=gothru.co) covers issues such as low resolution, duplicates, bad location information, and corrupt files. If imagery was removed for a [contributed-content policy](https://support.google.com/contributionpolicy/answer/7422880?hl=en&ref=gothru.co) violation, I address the underlying issue. Google decides what it displays.

If an image remains missing after a deliberate retry, I keep the tour ID, affected panorama, status, publish time, and public route together for GoThru support. I send those details privately. [GoThru Moderator](https://gothru.co/moderator.html?ref=gothru.co) is where I inspect, edit, and republish the connected tour, but the final Maps result is Google's decision.