Resources menu
All resources
Getting started
What is PageSoar?Try the PageSoar demoWhat's new in PageSoarRunning the free website checkYour first ten minutes in PageSoarWhat the Home screen showsHow the Getting started guide worksHow to choose your goalFinding and fixing
How a change goes live: draft, review, publish, checkWhat the agent changes by itself, and what waits for youWhat the SEO audit screen showsHow to find and filter your pagesWhat the page audit showsWhat site-wide issues mean and how to clear themHow to add internal links and untangle pages that competeHow page types are scored and how to change the standardsHow to change many pages at once with Bulk optimizeBroken links, redirects and page speedWhat the Market position screen showsHow to see what changed in your marketHow to choose your next movesHow to find sites that should link to youHow to check if Google's AI answers name youHow to choose what to write nextWhat the Meta Ads screen showsHow to save a filtered list as a viewProving it worked
How PageSoar measures whether a change workedHow to read the Did it work? screenWhat the Weekly briefing showsWhere your visits come from: the Channels screenHow to compare pages and build a dashboardWhich kinds of fix move clicks most: the Impact rankingHow to run a held-back experiment and log what you expectHow to track your search rankingsWhat the Needs attention screen is telling youHow to generate a report deckHow to be told when a number movesHow to log what you expect a change to doConnecting your site
Which sites PageSoar can publish toConnect Google Search Console and AnalyticsWhen a connection does not workHow to connect your website and GoogleHow to check your site's connection healthHow to request a custom connectorConnect WordPress to PageSoarConnect Ghost to PageSoarConnect a git repositoryConnect a Python appConnect Shopify to PageSoarConnect Webflow to PageSoarConnect Wix to PageSoarAsking your data
Asking your data in plain wordsHow to check a draft before it goes liveHow to check a rival's websiteSEO basics
What a title tag is and how to write a good oneWriting meta descriptions that earn clicksHeading structure: H1 to H3 explainedHow to write helpful image alt textWhat a canonical tag is and when to use itRedirects: 301 versus 302 and how to avoid chainsWhat an XML sitemap does and how to check yoursRobots.txt: what it blocks and common mistakesWhat structured data is and which types matter for a small businessHow to fix duplicate contentMobile-friendliness: what to checkHTTPS and why browsers warnWhat keyword research is and how to startSearch intent: the four kinds and how to match a page to oneLong-tail keywords for small businessesHow to write a page that answers a searchInternal linking basicsWhat backlinks are and how to earn them honestlyAnchor text explainedWhat E-E-A-T means in practiceContent refreshes: when and how to update an old pageKeyword cannibalization: how to spot and fix itLocal SEO basics and a Google Business Profile checklistHow to read a search results page (SERP features)Core Web Vitals explained: LCP, CLS and interaction speedHow to speed up a slow page: images, caching and scriptsWhat Google Search Console shows: queries, pages, clicks, impressions and positionWhat Google Analytics measures: users, sessions and eventsSetting up a conversion or key eventClick-through rate: what is normal and how to raise itBounce rate versus engagement rateUTM tags: tracking campaigns correctlyHow to run a simple before-and-after SEO test, and why correlation misleadsSeasonality: why traffic moves without any change from youWhat a Google algorithm update is and how to respondA monthly SEO reporting checklist for a small teamYour team and your data
Roles and approvalsIs my site safe with PageSoar?Billing, plans and cancellingHow to approve or send back a proposed changeAssigned and Decided: where your work and past decisions livePick the goal that counts as a winTeach PageSoar your brand voiceList what your product has todayCheck what PageSoar knows about your site and rivalsIgnore pages, or keep them out of GooglePublish your award badges so Google can show themCustom modules: parts built for your accountPeople, roles, company name and appearanceTarget site and the write testHow notifications and the weekly summary workHow to get back something you removedGlossary
SEO glossary A to ZRedirects: 301 versus 302 and how to avoid chains
A redirect sends visitors from one address to another, and choosing the right kind keeps your rankings and your leads.
What it is#
A redirect is an instruction from your server that says "this address has moved, go there instead". Visitors and search engines follow it without noticing. The two you meet most are the 301 redirect, which means moved permanently, and the 302 redirect, which means moved temporarily.
Why it matters#
When you rename a page, change your web address or move to a new site, the old address still has links, bookmarks and search results pointing at it. Without a redirect those people land on an error page and leave. With the right redirect they arrive where you want them, and search engines move the old address's standing to the new one.
How to check#
- Type the old address into your browser. Does it land on the right page?
- Open the browser's developer tools, go to the Network tab, reload, and read the status of the first request: 301 or 302.
- To see a chain, watch for more than one redirect in a row. Anything beyond one hop is worth fixing.
How to fix#
- Use 301 for permanent moves: a renamed page, a deleted page with a clear replacement, http to https, www to non-www.
- Use 302 only when the original will return, such as a short-term seasonal offer.
- Send each old address straight to its final destination. If A goes to B and B goes to C, change A to go to C, and keep B pointing at C.
- Redirect to the closest matching page, not always the home page.
- Update your own links to the new address so that visitors do not need the redirect at all. See redirect chain.
Redirects are usually set in your host's control panel, a redirect plugin, or a server file. Test after every change.
Common mistakes#
- Leaving a 302 in place for years on a move that is permanent.
- Building chains through successive redesigns. Each hop slows the page and risks a break.
- Making loops, where A goes to B and B goes back to A. Browsers show an error.
- Redirecting everything to the home page. Search engines may treat that as an error, and visitors do not find what they wanted.
- Forgetting redirects after a redesign, which is the most common way a business loses its search traffic overnight.
A broken address is a related problem; see broken links and page speed.