Can multiple users access a Google Search Console account?
Yes. A Google Search Console property owner can add multiple users and assign each person a permission level, such as owner, full or restricted access, so team members can view or manage SEO data without sharing login details.
Yes. A Google Search Console property can be accessed by multiple users, with each person given their own Google account and an appropriate permission level. This allows colleagues, agencies and developers to work with the same search performance data without sharing login credentials.
Access is assigned to a specific property rather than to Search Console as a whole. For example, permissions for a domain property may cover all protocols, subdomains and paths within that domain, while permissions for a URL-prefix property apply only to the specified URL scope.
Google Search Console permissions
- Owner: Has full control of the property, including managing users, settings and ownership. A verified owner proves control of the website through a verification method. A delegated owner receives owner-level access from an existing owner but does not necessarily have their own verification token.
- Full user: Can view all available data and use most Search Console tools and features. This is generally suitable for an SEO specialist, marketing manager or trusted agency that needs to investigate issues and manage reports.
- Restricted user: Can view most data but has limited access to sensitive features and actions. This is often appropriate for stakeholders who need reporting access without the ability to make changes.
Permission availability can vary slightly by property type and Search Console feature. Give each person the lowest level of access needed for their role, and use owner access only for people responsible for the website’s Search Console administration.
How to add a user
- Sign in to Google Search Console with an owner account.
- Select the relevant property from the property selector.
- Open Settings, then select Users and permissions.
- Select Add user.
- Enter the person’s Google account email address and choose their permission level.
- Save the change. The user can then sign in to Search Console with that Google account and select the property.
The email address must identify a Google account that the intended user can access. If a person works for an agency or supplier, add their individual business Google account where possible rather than sharing a company login. This creates a clearer audit trail and means access can be removed for one person without disrupting everyone else.
Managing access securely
- Review the user list when staff, contractors or agencies change roles.
- Remove access promptly when someone no longer works on the property.
- Do not share an owner’s password or verification files as a substitute for adding users.
- Limit owner access to trusted administrators, as owners can change important property settings and permissions.
- Use restricted access for people who only need to review performance, indexing or enhancement data.
- Check the correct property before adding a user, particularly where both a domain property and several URL-prefix properties exist.
Removing a user stops their direct access to the property, but it does not remove access they may have through another Google account, a separate property, or an organisation that manages the website. When completing an access review, check each relevant property and any ownership verification methods as well as the user list.
Multiple users can therefore work from the same Search Console property at the same time. Each user sees data according to their permission level, and changes such as submitting a sitemap or inspecting a URL are associated with the account that carries them out. Sharing access in this way keeps SEO reporting collaborative while preserving individual sign-in security and administrative control.
Multiple users can access the same Google Search Console property through their own Google accounts, with permissions assigned according to their responsibilities. This lets SEO specialists, developers and stakeholders work from the same data without sharing passwords or verification details.
For most team members, full or restricted access is more appropriate than owner access. Owners can manage users, settings and verification, so this level should be limited to trusted administrators. Review the property’s user list whenever a team member or supplier changes role, and remove access promptly when it is no longer required.