Why Are Google Street View Navigation Arrows Missing After Publishing?
Published panoramas but no navigation arrows? Use GoThru's Processing Pulse as aggregate context when deciding whether to wait or inspect the tour.
When Google Street View navigation arrows are missing after publishing, do not assume the tour failed. A GoThru example documents panoramas appearing before navigation was restored.[4] Google says published links may need up to four days to process.[2] The Pulse adds aggregate context but cannot diagnose a specific tour.
Street View navigation processing at a glance
| Question | Short answer |
|---|---|
| What is being processed? | The connections that let a visitor move between published 360 panoramas. |
| How long can it take? | Google says to allow up to four days after publishing connected Photo Spheres.[2] |
| Why are my panoramas visible without arrows? | GoThru has documented a case where panoramas appeared before navigation was restored, but the Pulse cannot identify the cause for a specific tour.[4] |
| What does the GoThru Pulse show? | Daily percentages of processed and waiting navigation records, selectable across 10, 20 or 30 days.[1] |
| Can the Pulse check my individual tour? | No. It shows an aggregate processing pattern, not the status of a particular tour. |
| Should I wait or repair the tour? | A broad delay signal is a reason not to assume the tour failed, but it does not rule out a tour-specific issue. Inspect the tour if the problem persists beyond Google's processing window or a specific image or connection is wrong. |
Open the live Google Street View Navigation Processing Pulse before using the guidance below. Its status and chart change as new daily data is added.
What does Street View navigation processing mean?
A connected Street View tour contains more than uploaded image files. Each 360 photo has metadata, including its geographic position and orientation, and may contain connections to other photos. Google's Street View Publish API represents those links as photo connections.[3]
After a third-party tool publishes the Photo Spheres and their links, Google still has to process what was submitted. Google Maps Help tells publishers to allow up to four days for connected Photo Spheres to be processed.[2]
That distinction explains a confusing result: individual panoramas can appear on Google Maps while the arrows or movement between them remain incomplete. A visible image is not proof that every connection has finished processing.
What is the GoThru Navigation Processing Pulse?
The GoThru Navigation Processing Pulse is a daily aggregate view of Street View navigation records presented by GoThru. It separates the share marked as processed from the share still waiting to be processed.[1]
The page provides:
- a current normal, warning or overloaded status;
- 10-day, 20-day and 30-day chart ranges;
- daily processed and not-processed percentages;
- a data-through date and countdown to the next scheduled page update;
- a multilingual interface that can follow the browser language or a manual selection.[1]
GoThru states on the page that it publishes 200–400 tours to Google Street View daily.[1] That is GoThru's first-party statement; the page does not say those tours are the chart's denominator. Although the public script exposes the rules used to assign Normal, Warning and Overloaded, it does not explain how each day's percentages are derived, expose raw record counts or provide a downloadable dataset. Treat the Pulse as a GoThru operational indicator, not an independent audit of Google's entire Street View system.
How to read the processing status
Normal
The page states that normal processing time is one to three days. In the public script, Normal is the fallback whenever neither the Warning nor Overloaded threshold is met. Google separately says to allow up to four days for published links to be processed.[1][2] Neither statement predicts when a specific tour will finish.
If the Pulse is normal and the tour was published recently, give Google time to complete processing. Avoid deleting and republishing a tour solely because its connections are still within Google's processing window.
Processing load is increasing
The public script sets the Warning state when more than 50% of records are not processed for at least two consecutive latest days, or when the latest day's not-processed share exceeds 90%.[1] This aggregate state does not predict when a specific tour will finish. Because one day above 90% can trigger the warning, a multi-day decline is not required.
Processing pipeline overloaded
The public script sets the Overloaded state after more than four consecutive latest days, meaning five or more daily records, with over 50% not processed.[1] This indicates broad processing pressure in GoThru's data; it does not establish the cause of any one tour's missing navigation.
The page also states that, at Google's request, GoThru reports a slowdown to its Google contact after the pipeline has been overloaded for 14 consecutive days.[1] This is the reporting process described by GoThru. It is not a guaranteed completion date or a way to prioritize an individual tour.
When should you wait, and when should you troubleshoot?
Use the tour symptom and the Pulse together.
| What you see | What it may mean | Next action |
|---|---|---|
| The panoramas and navigation were published less than four days ago | Google may still be processing the links | Wait and check the Pulse again after its next daily update |
| Several new tours show visible panoramas but missing arrows, and the Pulse shows a backlog | GoThru's aggregate data also shows processing pressure, but an individual tour may still have its own issue | Avoid assuming the tour failed; inspect it if the problem persists beyond Google's processing window |
| The Pulse is normal, but one tour still has a gap after the processing window | A panorama, connection or publication result may need attention | Check the specific tour with GoThru Street View Status |
| A panorama is missing from Google Maps | The image may be pending, rejected or absent rather than merely unconnected | Diagnose the missing panorama before repairing its links |
| Every panorama is present, but one arrow goes to the wrong place | The route may contain an incorrect connection or heading | Inspect the tour structure in GoThru Moderator, correct it and republish deliberately |
| A blue line created from uploaded video is still processing | This is a Street View Studio workflow, not the connected-panorama job measured by the Pulse | Diagnose the video and blue-line workflow separately |
| A driving-direction arrow is missing in the Google Maps app | This is a consumer navigation issue, not Street View tour processing | Use Google Maps app troubleshooting rather than the Pulse |
The Pulse is most useful as aggregate triage context. It shows whether GoThru's data also reflects processing pressure, but it does not replace inspection of the affected tour.
Why can panoramas appear before their navigation?
Google's Publish API represents a 360 photo resource and its connections[] field separately. That public data model shows connections are submitted as relationship data, but it does not describe Google's internal storage or processing order. Google retains control over what is published on Maps.[3]
GoThru's existing troubleshooting example also documents a case where individual panoramas appeared before Google restored all navigation connections.[4] This is an observed workflow example, not a universal timing rule.
Before deciding that the route is broken, check three separate states:
- Panorama presence: Is every expected 360 image visible on Google Maps?
- Navigation presence: Do movement arrows connect the visible panoramas?
- Navigation accuracy: Do the arrows lead to the intended next panorama and direction?
Each state has a different response. Waiting may be appropriate for still-processing navigation, but it will not repair a rejected panorama or an incorrectly built connection.
What the Processing Pulse does not tell you
The Pulse does not:
- display the status of a named tour, panorama or Google account;
- identify which connection is waiting;
- explain why Google rejected a panorama;
- monitor Street View Studio blue-line video processing or Google Maps driving directions;
- guarantee that navigation will finish within a specific number of hours or days;
- speed up, prioritize or manually complete Google's processing;
- replace the Street View Status tools used to inspect a GoThru tour.
It is also a GoThru page, not an official Google service-status dashboard. Google remains responsible for processing and for the final public state of contributed Street View imagery and connections.
A practical check after publishing a connected tour
- Preview the complete route in GoThru before publication. GoThru Moderator includes a preview step for checking connections before they are sent to Street View.[5]
- Record the publication time and keep the tour unchanged while initial processing is underway.
- Confirm that the expected panoramas appear on Google Maps.
- Test the route as a public visitor rather than only from the publishing account.
- If the panoramas are visible but navigation is missing, check the live Processing Pulse.
- Allow Google's published processing window before treating the delay as a broken tour.[2]
- If the Pulse returns to normal but one tour remains broken, inspect that tour with Street View Status.
- Repair only the affected panorama or connection, then republish and test the same route again.
This sequence helps you compare aggregate processing context with tour-specific evidence and avoids changing a correct tour solely because Google may still be processing it.
Frequently asked questions
How long does Google Street View navigation processing take?
GoThru describes one to three days as its normal observed range. Google Maps Help says to allow up to four days after connected Photo Spheres are published. These are processing guidelines, not guarantees for every submission.[1][2]
Why are my Street View panoramas visible but not connected?
A documented GoThru example shows panoramas appearing before all navigation was restored.[4] Check how recently the tour was published. Use the Pulse as aggregate context, then inspect the specific tour if the problem persists beyond Google's processing window.
Does missing navigation mean that Google rejected my panoramas?
No. A visible panorama with a missing arrow and a panorama absent from Google Maps are different conditions. If an image is missing, use Street View Status and the missing-images troubleshooting guide to inspect that panorama.
Is the GoThru Processing Pulse an official Google status page?
No. It is a GoThru operational page that summarizes processed and waiting navigation percentages. The page does not expose its raw record counts or full calculation method, so it should not be presented as a status report for every Google Street View contribution worldwide.
Can GoThru make Google process my tour faster?
The Pulse does not offer a speed-up or priority-processing control. Google controls its processing pipeline. During a broad delay, the practical action is usually to wait rather than repeatedly republish a tour that was built correctly.
When does GoThru report a processing slowdown?
The Pulse page states that GoThru reports the slowdown to its Google contact after the pipeline has remained overloaded for 14 consecutive days.[1] That reporting point does not guarantee when Google will clear the backlog.
Should I republish when navigation is missing?
Not immediately. First check the publication age, the Pulse and whether all panoramas are visible. Republish only when the broader pipeline is normal and inspection identifies a tour-specific image or connection that needs repair.
Where can I check the latest processing condition?
Use the Google Street View Navigation Processing Pulse. It shows the current status, recent daily percentages, selectable time ranges and the date through which the chart has data.
Check the processing pulse before rebuilding the tour
If a newly published tour has visible panoramas but missing navigation, do not assume the connection work failed. Check the live Navigation Processing Pulse, compare the recent trend and give Google its processing window.
When the Pulse is normal but one route remains broken, use GoThru Street View Status and the missing-images workflow to isolate the affected panorama. Use GoThru Moderator when the tour itself needs a connection, position or direction corrected before republishing.